mrichards42
commented
4 years ago I had a heck of a time getting a build to work on my Mac, but it sounds like we might have had different problems (I was mostly running into linker issues which turned out to be a problem with my PATH). I'm on 10.14.16 and Xcode 10.1, so it sounds like my experience might not match yours if it started failing after a build tools upgrade. I also never tried building for a 10.7 deployment target, only 10.14 -- are you saying that in your build XWord targets 10.7 but LuaJIT targets 10.14?
Getting things to build took enough time that once it I got it working I saved the the relevant env vars to a file and have been sourcing it before every build:
export CONFIGURATION=Debug
export PATH=/usr/bin:/bin:/usr/sbin:/sbin
export XWORD_VERSION=0.7.0-SNAPSHOT
export LUAJIT_VERSION=2.0.5
export WX_VERSION=3.1.3
export MACOSX_DEPLOYMENT_TARGET=10.14
# I expect everything below here is unnecessary, but I just snagged everything
# except DEPLOYMENT_TARGET from the travis logs and didn't try to pare it down
export CXX=g++
export CXX_FOR_BUILD=g++
export CC=gcc
export CC_FOR_BUILD=gccOther than that I've been pretty much following the commands you wrote in the travis file to a tee:
source the-above-env
bash build-luajit.sh $LUAJIT_VERSION
./build-wxwidgets.sh $WX_VERSION $CONFIGURATION
xcodebuild -project build/xcode4/XWord.xcodeproj -configuration "$CONFIGURATION" build
jpd236
In trying to resurrect my local Mac builds once again, I'm not able to get a build w/ Lua working correctly. It's still working fine with --disable-lua passed to premake. The first time I tried to launch Xcode, I had to take an update to the developer tools. Since then, I found that:
Trying to build LuaJIT fails without adding a MACOSX_DEPLOYMENT_TARGET=X flag. I built with 10.7 to try to match XWord (but also tried 10.14. 10.15 failed to build for me).
Trying to build XWord with the new LuaJIT binary crashes in wxlstate.cpp because luaL_newstate returns null. The only thing I can find about this online suggests that this could be because the needed 64-bit linker options (-pagezero_size 10000 -image_base 100000000) aren't set, but those are already in the premake config.
I tried updating Premake5 to alpha 15 and fixing the TODO to set the deployment target there using the systemversion config, so that I can use the 10.7 deployment target, but that didn't seem to do it.
Not sure I have many more ideas off the top of my head... I can of course still run the 0.7.0 build just fine, but not sure how to run a fresh local build.