пт, 5 дек. 2025 г., 06:35 Rob Prowel via Cin <[email protected]>:
> On 12/4/25 10:17 PM, Andrew Randrianasulu wrote: > > > > > You mean this diff? > > > > > > https://github.com/mpruett/audiofile/commit/ > > b62c902dd258125cac86cd2df21fc898035a43d3.diff <https://github.com/ > > mpruett/audiofile/commit/b62c902dd258125cac86cd2df21fc898035a43d3.diff> > > > > yes, I downloaded it and cut out Changelog entry. > > > > will try on my main desktop today ... and if worked will send as patch > > against our sources. > > > > > > Yep. That would be it. I hacked the Makefile to add -fpermissive as a > work-around but yes, pulling the patch would make more sense. > > > > re - nv-codec-headers. Yes, there is an updated git repo on > videolan.org and the minimum version has moved to 13.0. > > 1) So where are we on this? your git reference is not from > videolan.org? What are you treating as the authoritative source, or > should I wait until ALL considered changes appear In the cingg git repo? > Versions and download locations should all be in: cinelerra/cinelerra-5.1/thirdparty/downloads.txt > 2) Are you running into cases where you "cant" simply upgrade the tools > because of a need to support legacy? > yes. > My concern in patching these things in here to test them out is that I > don't want to have to do a full make clean; make to test out changes: > takes way too long. > > 3) Are there any make targets that intelligently build just the > thirdparty libs that have changed? > you can rm -rf thirdparty/lib_you_want_gone then rm thirdparty/build/lib_you_want_gone.* (there usually 3 of them, each appearing as unpacking, patching, compiling happens). After this restarting from level where you ran ./autogen.sh will use all configured cpus for re-unpacking, patching, compiling, linking specific subproject in thirdparty. if you step in cinelerra/ and do "make" without any -j there it will go for single make job as default. Not sure what will happen if you try to manually build thirdparty libs this way .... If you have enough storage you can try ccache, set it as your CC before compile so recompile will be faster. export CC="ccache gcc" I also have ~/.cache/ccache/ccache.conf with those lines: compression = true compression_level = 8 depend on cpu power and hdd space you can try something like this. > 4) Can I change parallel jobs make count after ./configure stage? I > needs to be (one) during debugging, but (max-cpu) when trying to do a > quick compile. > > > > > _______________________________________________ > Cin mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
