From 40bebd3aa314bb78a3e359264ad6abd93fbb85e5 Mon Sep 17 00:00:00 2001 From: Robin Watts Date: Thu, 3 Nov 2016 12:43:59 +0000 Subject: MSVS: Add libluratech to project. 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. --- platform/win32/libfonts.vcproj | 244 ----------------------------------------- 1 file changed, 244 deletions(-) (limited to 'platform/win32/libfonts.vcproj') diff --git a/platform/win32/libfonts.vcproj b/platform/win32/libfonts.vcproj index bd9f9c12..b15dfaac 100644 --- a/platform/win32/libfonts.vcproj +++ b/platform/win32/libfonts.vcproj @@ -384,250 +384,6 @@ Name="VCPostBuildEventTool" /> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- cgit v1.2.3