| Age | Commit message (Collapse) | Author |
|---|
|
Looks like x64 ones didn't 'stick' last time I edited them.
|
|
Having libluratech set to not build in non-commercial builds is
not enough to make stuff work, as the dependencies will still
try to link it in.
Instead, we now have a Release configuration for libluratech
with every file disabled, and the non-commercial builds depend
on that.
Also, tweak bin2coff build to put it's buildlog in the usual
place.
|
|
|
|
Keeping them up to date is difficult and prone to errors, so we move
setting the USE_OUTPUT_DEBUG_STRING and FZ_LARGEFILE flags to the source
instead of relying on project file definitions.
|
|
Also tweak dependencies to avoid strange build problems
for Commercial builds.
|
|
This will only be built in "DebugCommercial" "ReleaseCommercial" and
"MementoCommercial" configuration builds.
A note on the way MSVS solutions work; libluratech is listed as
a dependency of the executables - this applies to ALL configurations.
In order to stop normal builds failing when we have no source, we
set each non "Commercial" configuration to not build libluratech.
The linker still looks for the output from the libluratech stage
to link in though, so for all non "Commercial" configurations, we
have the libluratech stage set to produce output named " ". This
is copied into the linker command line, and all is happy.
The sole downside to this is that if we try to build libluratech
in "Debug" (say) rather than "DebugCommercial", the build will
fail at the library making step. This will never happen unless
we manually try to build that project in that configuration though.
|
