Fwd: cingg freebsd 12.3 (amd64)
compiles under freebsd 12.3/amd64 as well... ---------- Forwarded message ---------- From: *Андрей Рандрианасулу* <[email protected]> Date: Tuesday, March 29, 2022 Subject: cingg freebsd 12.3 (amd64) To: randrianasulu <[email protected]> https://cloud.mail.ru/public/MW5Q/NvWMhahR4 sha256sum /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz 1e4e56aa5eff24e7cdee16b027e4181e3d50948450b6a279e815ef925349ed2d /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz -- Андрей Рандрианасулу
Andrew, I downloaded both cin-freebsd-12.3.tar.xz and cingg-freebsd-13.tar.xz . Is it OK to put on Cinelerra's website and mention it in the manual? On Tue, Mar 29, 2022 at 10:14 AM Andrew Randrianasulu via Cin < [email protected]> wrote:
compiles under freebsd 12.3/amd64 as well...
---------- Forwarded message ---------- From: *Андрей Рандрианасулу* <[email protected]> Date: Tuesday, March 29, 2022 Subject: cingg freebsd 12.3 (amd64) To: randrianasulu <[email protected]>
https://cloud.mail.ru/public/MW5Q/NvWMhahR4
sha256sum /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz 1e4e56aa5eff24e7cdee16b027e4181e3d50948450b6a279e815ef925349ed2d /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz -- Андрей Рандрианасулу
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On Wednesday, March 30, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, I downloaded both cin-freebsd-12.3.tar.xz and cingg-freebsd-13.tar.xz . Is it OK to put on Cinelerra's website and mention it in the manual?
as user-contributed.. (I mean I only have guest-ish VM setup for testing, and not really prolonged bsd user - builds works for very simple things I tried for 5 minutes, but any further testing better to be done by more experienced users and on real hardware..)
On Tue, Mar 29, 2022 at 10:14 AM Andrew Randrianasulu via Cin < [email protected]> wrote:
compiles under freebsd 12.3/amd64 as well...
---------- Forwarded message ---------- From: *Андрей Рандрианасулу* <[email protected]> Date: Tuesday, March 29, 2022 Subject: cingg freebsd 12.3 (amd64) To: randrianasulu <[email protected]>
https://cloud.mail.ru/public/MW5Q/NvWMhahR4
sha256sum /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz 1e4e56aa5eff24e7cdee16b027e4181e3d50948450b6a279e815ef925349ed2d /home/guest/cin_bsd/cin-freebsd-12.3.tar.xz -- Андрей Рандрианасулу
-- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
Andrew
On Wednesday, March 30, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, I downloaded both cin-freebsd-12.3.tar.xz and cingg-freebsd-13.tar.xz . Is it OK to put on Cinelerra's website and mention it in the manual?
as user-contributed.. (I mean I only have guest-ish VM setup for testing, and not really prolonged bsd user - builds works for very simple things I tried for 5 minutes, but any further testing better to be done by more experienced users and on real hardware..)
Hoping I can eventually install bsd 13 and test this though (but may be a
long time from now as I want to get aarch64 and termux tested first). Anyway, I took your BSD patches 0001 through 0017 + 0018 that I made from the link in "one more bsd patch email" + plugins_makefile_freebsd.diff and put them all in 1 big file, bsd13.patch (like current blds/bsd.patch) but get a lot of rejections. That is OK, I will work it out but just wanted to let you know what I was doing. ...Phyllis
On Thursday, March 31, 2022, Phyllis Smith <[email protected]> wrote:
Andrew
On Wednesday, March 30, 2022, Phyllis Smith <[email protected]> wrote:
Andrew, I downloaded both cin-freebsd-12.3.tar.xz and cingg-freebsd-13.tar.xz . Is it OK to put on Cinelerra's website and mention it in the manual?
as user-contributed.. (I mean I only have guest-ish VM setup for testing, and not really prolonged bsd user - builds works for very simple things I tried for 5 minutes, but any further testing better to be done by more experienced users and on real hardware..)
Hoping I can eventually install bsd 13 and test this though (but may be
a long time from now as I want to get aarch64 and termux tested first).
for freebsd I cheated and used pre-installed image from https://download.freebsd.org/releases/VM-IMAGES/13.0-RELEASE/amd64/Latest/ https://download.freebsd.org/releases/VM-IMAGES/13.0-RELEASE/amd64/Latest/Fr... download, unxz, run as qemu-system-x86_64 -hda file -enable-kvm -m 1024 -smp 2 it will boot into console, login as root then you can 'pkg install somepackage' or delete some stuff (root power!) startx will start x with few xterms. you can create ~/.xinitrc with your commands, like I put 'xrandr - s 3' {smaller 1024x768 resolution for my smaller host scren} and 'startfluxbox' there (after pkg install xorg, pkg install fluxbox). start x with 'startx' devices are automanaged, so you will see only small number of files in /dev ada0p1- p4 - your first disk, ada1p{0-4} second. (if you attach it via-hdb switch at qemu start) just mount them somewhere, I mounted into /mnt
Anyway, I took your BSD patches 0001 through 0017 + 0018 that I made from the link in "one more bsd patch email" + plugins_makefile_freebsd.diff and put them all in 1 big file, bsd13.patch (like current blds/bsd.patch) but get a lot of rejections. That is OK, I will work it out but just wanted to let you know what I was doing. ...Phyllis
my idea was to augment code and makefiles so bsd patch eventually will be unneeded. my patches for 'git am'. surely for next month+! this monthly build I only hope to have in fix for libdav1d 1.0.0 - gentoo and termux moved on because their ffmpeg was already patched/ready
Outdated reply (forgot to hit Send yesterday). Bottom line is that _10 is in the new releases and checked into GIT.
this monthly build I only hope to have in fix for libdav1d 1.0.0 - gentoo and termux moved on because their ffmpeg was already patched/ready
Uh oh, I downloaded your libdav1d patch #10 dated March 27, but never got it tested and tomorrow I have to create the appimages. Am building with that in now. BTW patch_10 is a weird name when we have patchA. my idea was to augment code and makefiles so bsd patch eventually will be
unneeded. my patches for 'git am'. surely for next month+!
OK, sounds good.
On Thursday, March 31, 2022, Phyllis Smith <[email protected]> wrote:
Outdated reply (forgot to hit Send yesterday). Bottom line is that _10 is in the new releases and checked into GIT.
this monthly build I only hope to have in fix for libdav1d 1.0.0 - gentoo and termux moved on because their ffmpeg was already patched/ready
Uh oh, I downloaded your libdav1d patch #10 dated March 27, but never got it tested and tomorrow I have to create the appimages. Am building with that in now. BTW patch_10 is a weird name when we have patchA.
i have pile of bluray-related ffmpeg patches in between git head and this patch.. thanks for adding it!
my idea was to augment code and makefiles so bsd patch eventually will be
unneeded. my patches for 'git am'. surely for next month+!
OK, sounds good.
i have pile of bluray-related ffmpeg patches in between git head and this patch..
Yeah, I know and have downloaded everything you have sent so far. It is really bothering me because I can not keep up and I do not want to lose any new work. So here is what I can remember that is still on the list to be done. It is really necessary for new things that go in to at least be checked by one other person and for bluray, that is me because not too many people use it anymore. I still do though.
1) anuel has updated *OpenEXR* version and this need to be done soon. 2) Manual also created *DPX list *code that is valuable and appreciated and I want to get this in. (see Andrea earlier email). 3) Testing *Termux *on an Android tablet still stalled due to time constraints. 4) QEMU install of an *aarch64 system* as provided by MatN so I can create monthly AppImages (time constraints too). 5) Test all the *bluray patches *and check out that "pcm bluray" email. Probably more that I have simply forgotten.
On Thursday, March 31, 2022, Phyllis Smith <[email protected]> wrote:
i have pile of bluray-related ffmpeg patches in between git head and this
patch..
Yeah, I know and have downloaded everything you have sent so far. It is really bothering me because I can not keep up and I do not want to lose any new work. So here is what I can remember that is still on the list to be done. It is really necessary for new things that go in to at least be checked by one other person and for bluray, that is me because not too many people use it anymore. I still do though.
1) anuel has updated *OpenEXR* version and this need to be done soon.
note, new (thirdparty) openexr may drag in new cmake/compiler requirements. 2) Manual also created *DPX list *code that is valuable and appreciated and
I want to get this in. (see Andrea earlier email).
only reading last time I checked? (need to recheck, also c++17 bar...)
3) Testing *Termux *on an Android tablet still stalled due to time constraints.
you can install android-tools (slackware/salix name) and use 'adb push' and 'adb pull' via usb cable or even via wifi
4) QEMU install of an *aarch64 system* as provided by MatN so I can create monthly AppImages (time constraints too).
yeah, emulation is slow, but hopefully can be left running literally overnight (or even over weekend) 5) Test all the *bluray patches *and check out that "pcm bluray" email.
Probably more that I have simply forgotten.
freebsd/netbsd/non-x86 bringup :-)
participants (2)
-
Andrew Randrianasulu -
Phyllis Smith