I was just pointed at 'filesystem' module reimplementation for c++11 and up:<div><br></div><div><a href="https://github.com/justdan96/tsMuxer/issues/577">https://github.com/justdan96/tsMuxer/issues/577</a></div><div><br></div><div><a href="https://github.com/gulrak/filesystem">https://github.com/gulrak/filesystem</a></div><div><br><br>On Monday, March 28, 2022, mnieuw--- via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, you really need patchelf, it is called from within.<br>
<br>
The original appimage version of linuxdeploy builds it from sources<br>
because for a appimage the executables needs to be statically linked,<br>
and the system version isn't.<br>
Indeed two boost dev libs are needed too. I dislike then, not because<br>
the API is unstable (did not know that), but because they are so bug<br>
and (for me) difficult to follow what they actually do. Maybe they can<br>
be taken out, but the filesystem one does more that I thought it does.<br>
Maybe for a next release.<br>
<br>
MatN<br>
<br>
On Sun, 27 Mar 2022 18:07:36 -0600<br>
Phyllis Smith via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br>
<br>
> Andrew, thanks! I thought having "boost" installed was sufficient, but<br>
> apparently for Fedora I had to do "dnf install libbost-devel". So<br>
> got past that. Let me see I really have to have "patchelf"<br>
> installed or what its name is.<br>
> <br>
> On Sun, Mar 27, 2022 at 5:56 PM Andrew Randrianasulu <<br>
> <a href="mailto:randrianasulu@gmail.com">randrianasulu@gmail.com</a>> wrote: <br>
> <br>
> ><br>
> ><br>
> > On Monday, March 28, 2022, Phyllis Smith via Cin <<br>
> > <a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br>
> > <br>
> >> MatN, I have not been able to figure out what is wrong. See error<br>
> >> below (from running bld_own_appimage.sh with the compiling of<br>
> >> CinGG being commented out as it was already done several times):<br>
> >> <br>
> >>> [root@keystone cinelerra-5.1]# ./bld_own_appimage.sh<br>
> >>> target = x86_64<br>
> >>> configure script options are --with-single-user --with-booby<br>
> >>> --enable-static-build<br>
> >>> <a href="http://configure.ac:19" target="_blank">configure.ac:19</a>: installing 'cfg/compile'<br>
> >>> <a href="http://configure.ac:12" target="_blank">configure.ac:12</a>: installing 'cfg/install-sh'<br>
> >>> <a href="http://configure.ac:12" target="_blank">configure.ac:12</a>: installing 'cfg/missing'<br>
> >>> Makefile.am: installing 'cfg/depcomp'<br>
> >>> checking for a BSD-compatible install... /usr/bin/install -c<br>
> >>> checking whether build environment is sane... yes<br>
> >>> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p<br>
> >>> checking for gawk... gawk<br>
> >>> checking whether make sets $(MAKE)... yes<br>
> >>> <br>
> >> checking whether make supports nested variables... yes <br>
> >>> checking for g++... g++<br>
> >>> checking whether the C++ compiler works... yes<br>
> >>> checking for C++ compiler default output file name... a.out<br>
> >>> checking for suffix of executables...<br>
> >>> checking whether we are cross compiling... no<br>
> >>> checking for suffix of object files... o<br>
> >>> checking whether we are using the GNU C++ compiler... yes<br>
> >>> checking whether g++ accepts -g... yes<br>
> >>> checking whether make supports the include directive... yes (GNU<br>
> >>> style) checking dependency style of g++... gcc3<br>
> >>> checking for gcc... gcc<br>
> >>> <br>
> >> checking whether we are using the GNU C compiler... yes <br>
> >>> checking whether gcc accepts -g... yes<br>
> >>> checking for gcc option to accept ISO C89... none needed<br>
> >>> checking whether gcc understands -c and -o together... yes<br>
> >>> checking dependency style of gcc... gcc3<br>
> >>> checking how to run the C preprocessor... gcc -E<br>
> >>> checking how to run the C++ preprocessor... g++ -E<br>
> >>> checking for grep that handles long lines and -e... /usr/bin/grep<br>
> >>> checking for egrep... /usr/bin/grep -E<br>
> >>> checking for ANSI C header files... yes<br>
> >>> checking for sys/types.h... yes<br>
> >>> checking for sys/stat.h... yeschecking for stdlib.h... yes<br>
> >>> checking for string.h... yes<br>
> >>> checking for memory.h... yes<br>
> >>> checking for strings.h... yes<br>
> >>> <br>
> >> checking for inttypes.h... yes <br>
> >>> checking for stdint.h... yes<br>
> >>> checking for unistd.h... yes<br>
> >>> checking boost/filesystem.hpp usability... no<br>
> >>> checking boost/filesystem.hpp presence... no<br>
> >>> checking for boost/filesystem.hpp... no<br>
> >>> *configure: error: header is missing and required.*<br>
> >>> make: *** No targets specified and no makefile found. Stop.<br>
> >>> objcopy: 'makeappimage': No such file<br>
> >>> mv: cannot stat 'makeappimage': No such file or directory<br>
> >>> ./bld_own_appimage.sh: line 60: tools/makeappimage: No such file<br>
> >>> or directory<br>
> >>> <br>
> >> <br>
> > guess boost headers not installed. I dislike libboost as dependency<br>
> > (due to unstable api!) but may be in this case copying relevant<br>
> > headers will be enough?<br>
> ><br>
> ><br>
> ><br>
> > <br>
> >><br>
> >><br>
> >> On Fri, Mar 25, 2022 at 4:34 AM M Nieuwenhoven via Cin <<br>
> >> <a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br>
> >> <br>
> >>> Attached is a 7z file that allows CinelerraGG in AppImage format<br>
> >>> to be built on aarch64, as well as x86 64 and 32 bit.<br>
> >>> Ir replaces linuxdeploy which was used since we switched to<br>
> >>> AppImage format a year ago, but that is not available for non-x86<br>
> >>> platforms. The new tool called makeappimage (800k) is built<br>
> >>> automatically when needed, and is a stripped-down version of<br>
> >>> linuxdeploy: its plugin-system has been removed, and the built<br>
> >>> system switched to the much simpler autotools (like CinGG<br>
> >>> itself). It is put in a new CinGG subdirectory calls tools (but<br>
> >>> for now this is the only tool :-) ). To install, place the .7z<br>
> >>> file in the cinelerra5/cinelerra directory, and do "7z x<br>
> >>> bld_own_appimage.7z " . To use it, use the included<br>
> >>> ./bld_own_appimgage.sh . Name of the script should be changed in<br>
> >>> the future to "bld_appimage.sh" if OK for all. Make sure the<br>
> >>> appimagetool for the platform is in your path, see the note in<br>
> >>> bld_own_appimage.sh .<br>
> >>><br>
> >>> The script also changes the configure script options depending on<br>
> >>> the hardware it is running on. @Andrew_R, does it need extra<br>
> >>> things for termux?<br>
> >>><br>
> >>> MatN--<br>
> >>> Cin mailing list<br>
> >>> <a href="mailto:Cin@lists.cinelerra-gg.org">Cin@lists.cinelerra-gg.org</a><br>
> >>> <a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" target="_blank">https://lists.cinelerra-gg.<wbr>org/mailman/listinfo/cin</a><br>
> >>> <br>
> >> <br>
<br>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" target="_blank">https://lists.cinelerra-gg.<wbr>org/mailman/listinfo/cin</a><br>
</blockquote></div>