2017-02-21 12:35:37 UTC
I've spend 10+ hours on trying to build binaries for Flowblade
AppImage. I can get MLT and modules to build but there is problem I
can't figure out, so I decided just to ask for help as a Python/Java
developer I'm not sure how to proceed.
AppImage project provided a recipe to build Flowblade AppImage but it
uses Ubuntu 14.04 binaries with MLT 0.9.0 and that's too old to
So my approach has been:
- create Appimage with the Recipe I got
- build MLT 6.4.1 with dependencies from repository
- replace binaries in Appimage .AppDir with ones I've build my self
- rebuild Appimage
I used your Flowblade build script as a starting point to get the
configure flags etc.
It all works, I get all required binaries replaced, but when running
AppImage I get "mlt_repository_init: no plugins found in
so I've obivously compiled my dev system paths into binaries.
Your build-script from flowblade had line: export
LD_RUN_PATH="$FINAL_INSTALL_DIR/lib" but I'm not using that.
To get everything compiled I'm running 'make install' to make
everything compile, with configure --prefix=<my work dir/build> so
this is where to paths go in, but this is needed (I think) to have
includes and .pc files available during compilation.
To get stuff working with appimage I need to compile MLT that installs
So to move forward, I ask:
- is there some combination of "--prefix, --libdir, export CFLAGS=,
export LDFLAGS=, export PKG_CONFIG_PATH=" I can set to make this
happen or is MLT build system such that this hard
- is it just better to compile and install the whole thing in a
virtual machine or chroot env with "--prefix/usr/lib/x86_64-linux-gnu"
and copy binaries from that system.
- is there some othe approach that might be best
I obviously suck at this big time, but any help here would greatly appreciated.
I you like to see my build scripts, they are at: