When cross compiling bzip2, it may use host tools such as ranlib instead
of the cross tools.
Apply the msys2 autotools patch to the cross bzip2 and move it to after
automake in the chain.
- add python2 for msys to list of core deps and link it to root/bin,
harfbuzz requires python to build
- fix double eval in build_project()
- remove duplicates from list of host-only and host/target dists in
mingw.sh
- fix msys2-builder startup, and assume 64 bit build if MSYSTEM = MSYS
- make sure MSYS has winsymlinks:nativestrict on startup, the user has
to turn off UAC
- update patch for infozip zip to fix a #define
Overall, the script is far too slow to be practical.
TODO: build both python and perl for the host to not rely on system
versions
under `tools/` add some scripts to invoke the build system to build all
deps for vbam and vbam itself:
- `tools/linux/builder`
This builds a mostly static linux binary with a few dynamic deps for
xorg and wayland. Using gtk3. This will run on just about any dist.
- `tools/osx/builder`
Builds a static mac app targetting 10.7.
- `tools/win/linux-cross-builder`
Builds a static windows binary using the mingw-w64 toolchain.
- `tools/win/msys2-builder`
Builds a static windows binary in the MSYS2 environment, this may be
suffering from a few regressions.
Change some cmake code to support the build system, refactor a few
things in it.
Rafael Kitover