- Feb 25, 2016
-
-
Nat Goodspeed authored
-
- Feb 23, 2016
-
-
Nat Goodspeed authored
-
- Feb 18, 2016
-
-
Nat Goodspeed authored
Eliminate mention of CMake specific-version Visual Studio generator: let it use the most recently-installed version of VS.
-
- Feb 17, 2016
-
-
Nat Goodspeed authored
Guessing that perhaps build_variables_checkout is inherited as is (lowercase) from build.sh on Mac and Linux, whereas Windows capitalizes it along the way.
-
Nat Goodspeed authored
-
Nat Goodspeed authored
-
- Feb 12, 2016
-
-
Nat Goodspeed authored
Otherwise fall back on ../build-variables as before. A TC build host doesn't literally check out build-variables et al. as siblings to the repository being built, but it does set environment variables to them.
- Feb 05, 2016
-
-
Nat Goodspeed authored
Remove Debug builds from build-cmd.sh and autobuild.xml. Comment out minizip builds from build-cmd.sh and autobuild.xml. (We're not sure whether we're going to have to reinstate minizip.) Use $LL_BUILD to apply relevant compiler switches to CFLAGS and CXXFLAGS for Linux configure.
-
Nat Goodspeed authored
Therefore using $AUTOBUILD_WIN_VSPLATFORM for that middle subdirectory name is incorrect.
-
- Feb 04, 2016
-
-
callum_linden authored
-
callum_linden authored
-
callum_linden authored
-
- Feb 03, 2016
-
-
Nat Goodspeed authored
Add requirement for sibling checkout of build-variables repo. Bring in those variables. Make the platform 'case' statement handle windows64, darwin64, linux64 -- instead of skipping all build activity for those as it did before! Adapt Mac configure variables CFLAGS and LDFLAGS to vary -arch depending on AUTOBUILD_ADDRSIZE. Use LL_BUILD from build-variables/convenience for the rest. Fix script bug in which install_name was set after use, causing the linker to stamp the dylib with an empty -install_name. For AUTOBUILD_ADDRSIZE=64, add --64 switch to configure. Comment out all Mac Debug build and test activity. (Copy a couple script comments from the Debug block to the Release block.) Comment out anything to do with contrib/minizip. Remove debug and minizip items from the darwin manifest in autobuild.xml. Use awk to extract the section of the README containing the copyright info, rather than using 'tail -n 31', which would break if the README contents change with updated versions of the upstream software.
-
- Jan 28, 2016
-
-
Nat Goodspeed authored
instead of deriving those values "by hand" from AUTOBUILD_ADDRSIZE.
-
Nat Goodspeed authored
-
- Jan 27, 2016
-
-
Nat Goodspeed authored
-
- Nov 19, 2014
-
-
Nat Goodspeed authored
On Windows, autobuild primes the AUTOBUILD environment variable with a Windows-style pathname. Unfortunately, when it's a bash script (such as build-cmd.sh) trying to invoke "$AUTOBUILD", this only confuses the issue. Use cygpath -u to convert back to a pathname bash can handle.
-
- Oct 31, 2014
-
-
Nat Goodspeed authored
Also from minizip/Makefile.Linden.Win32.mak, where I'd inserted it earlier to be able to link the utility programs with the library. It's not clear at what point the upstream project decided that ZLIB_WINAPI should be the default for all Windows builds, but it wreaks havoc on our viewer build dependency tree: when zlib is built that way, every 3p library that depends on it must ALSO #define ZLIB_WINAPI to be able to link with it. Cheaper to undo the macro in the zlib repo than to fix every consumer.
-
- Oct 15, 2014
-
-
Nat Goodspeed authored
AUTOBUILD_VSVER should be set by the project in general; an individual repo should only override it if that library must be built with a *different* version of Visual Studio for some weird reason.
-
- Oct 13, 2014
-
-
Nat Goodspeed authored
Also remove diagnostic output intended to help identify The Wrong CMake.
-
- Oct 10, 2014
-
-
Nat Goodspeed authored
-
Nat Goodspeed authored
zlib.lib is built with __stdcall. Unless we specify ZLIB_WINAPI on the mini{zip,unz}.exe builds, it thinks zlib entry points are __cdecl and fails to link those symbols.
-
Nat Goodspeed authored
The assembler sources are built without SAFESEH; attempting to link them with the C++ code produces link errors unless the C++ is also built without SAFESEH.
-
Nat Goodspeed authored
-
Nat Goodspeed authored
We realize that's not the real solution -- it's fragile, won't necessarily work on other hosts -- but it should at least let us know whether fixing the PATH will succeed, or whether there are other errors that must be addressed... such as incompatibilities between CMake 2.8.x and CMake 3.0.x. Also dump the PATH.
-
- Oct 09, 2014
-
-
Nat Goodspeed authored
-
Nat Goodspeed authored
-
Nat Goodspeed authored
Without that cmake step, the repo contains no zconf.h, and multiple compiles fail.
-
- Sep 27, 2014
- Sep 26, 2014
-
-
obscurestar authored
-
- Sep 24, 2014