Switch from asmjs-unknown-emscripten for Emscripten builds to using
asmjs-local-emscripten instead. The config.sub script doesn't recognize
the emscripten "CPU type" and throws an error, but changing to *-local-*
instead overrides its normal checks.
This call sets various environment variables (including PATH) before
install; it's important this happens here as well as for build, because
the install step may require tools installed in the install.native
directory.
Since the working directory can be changed it is not valid to use
$0 to reinvoke the script. This fixes#14 - thanks to @KingOfPoptart
for the bug report.
The ordering here is important, otherwise the Linux path in buildenv.sh
tries to use the INSTALL_DIR variable and fails.
This fixes#15. Thanks @cvanderw for the report.
If a package is not defined correctly (eg. wrong pkg-config name),
chocpkg might not recognize a package is installed even after we've
gone through the entire build and install step. So print a message if
'chocpkg installed' still evaluates to false after install.
Don't make or commit merges when running 'git pull' - the assumption
is that we're tracking an upstream branch that should always be
possible to fast-forward. Better to fail with an error if we can't
do this and allow the user to intervene to resolve the problem.
The current download URL linked from the front page is unstable, since
it breaks every time a new release is put out. Instead, link to the
/fossils/ directory, which contains all old releases as well as the
current release.
Using LDFLAGS ought to work, but libtool strips it out when compiling,
so it doesn't. Instead, set the CC variable so that it is always used.
This fixes the dependency on the libgcc DLL on Windows.
The package group version of this function is identical to the normal
command, so it isn't necessary. Plus it's not clear that there's a
need for a hook on the dependencies command.
It's not enough to pass $PACKAGE_NAME when recursing to invoke a
subcommand. Since PACKAGE_NAME now just includes the base package
name with no qualifiers, the type and variant will be lost. Instead,
be more explicit about always passing a fully-qualified name to the
sub-process.
We already target the OS X 10.7 API, and 10.7 won't run on machines
that don't have a 64-bit-capable processor. So there's no reason not
to do this now.
chocolate-doom sdl2-branch no longer depends on SDL2_image as of commit
chocolate-doom/chocolate-doom@7215d13b6c, so remove this dependency
and the SDL2_image package.
Normally we run ./configure from within the build tree, but autotools
now allows doing out-of-tree builds by running configure while cd'ed
to a different directory. Add a config variable `AUTOTOOLS_BUILD_PATH`
to allow this on a per-package basis, and set this for the SDL2
package; SDL2 hg complains when doing in-tree builds because certain
files get clobbered.
