1c7167e9ac
Make sure we include any user-specified project settings in our project definitions, this way users can customize their VS environment to more closely match what they're building for, and they better can control debugging and deployment from VS. Add support for setting VS-only compiler defines, include paths, and additional linker options, as a hint to VS to use when loading projects and parsing code. VS would usually know these on non nmake projects, but for nmake projects we have to tell it about any implicit information that the compiler has, so it can resolve symbols in the editor.
21 lines
No EOL
1.1 KiB
XML
21 lines
No EOL
1.1 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<Project ToolsVersion="17.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
|
|
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='%%VSCONF%%'">
|
|
<NMakeBuildCommandLine>%%BUILD%%</NMakeBuildCommandLine>
|
|
<NMakeReBuildCommandLine>%%REBUILD%%</NMakeReBuildCommandLine>
|
|
<NMakeCleanCommandLine>%%CLEAN%%</NMakeCleanCommandLine>
|
|
<NMakeOutput Condition="'$(NMakeOutput)' == ''">%%OUTPUT%%</NMakeOutput>
|
|
<NMakePreprocessorDefinitions>%%DEFINES%%;$(NMakePreprocessorDefinitions)</NMakePreprocessorDefinitions>
|
|
<NMakeIncludeSearchPath>%%INCLUDES%%;$(NMakeIncludeSearchPath)</NMakeIncludeSearchPath>
|
|
<NMakeForcedIncludes>$(NMakeForcedIncludes)</NMakeForcedIncludes>
|
|
<NMakeAssemblySearchPath>$(NMakeAssemblySearchPath)</NMakeAssemblySearchPath>
|
|
<NMakeForcedUsingAssemblies>$(NMakeForcedUsingAssemblies)</NMakeForcedUsingAssemblies>
|
|
<AdditionalOptions>%%OPTIONS%% $(AdditionalOptions)</AdditionalOptions>
|
|
</PropertyGroup>
|
|
<PropertyGroup Condition="%%CONDITION%%">
|
|
%%PROPERTIES%%
|
|
</PropertyGroup>
|
|
<ItemGroup Condition="%%CONDITION%%">
|
|
%%EXTRA_ITEMS%%
|
|
</ItemGroup>
|
|
</Project> |