[Cin] Build update

[mnieuw at zap.a2000.nl]

Yes, you really need patchelf, it is called from within.

The original appimage version of linuxdeploy builds it from sources
because for a appimage the executables needs to be statically linked,
and the system version isn't.
Indeed two boost dev libs are needed too. I dislike then, not because
the API is unstable (did not know that), but because they are so bug
and (for me) difficult to follow what they actually do. Maybe they can
be taken out, but the filesystem one does more that I thought it does.
Maybe for a next release.

MatN

On Sun, 27 Mar 2022 18:07:36 -0600
Phyllis Smith via Cin <cin at lists.cinelerra-gg.org> wrote:

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