From 0aa440a22ab18bc4a9077fcf17966ed4949d684b Mon Sep 17 00:00:00 2001
From: Tim Foley <tfoley@nvidia.com>
Date: Mon, 25 Sep 2017 09:35:34 -0700
Subject: Fixup: deal with hitting `.obj` size limits for VS

When using the lumped/"unity" build approach for Slang, the resulting `.obj` files run into number-of-sections limits in the VS linker. For now I'm using the `/bigobj` command-line flag to work around this for the `hello` example, just so I can be sure the lumped build still works, but longer term it seems like we need to just drop that approach anyway.

The `render-test` application was switched to link against `slang.dll` since there is no reason to have multiple apps use the lumped approach.
---
 tools/render-test/render-test.vcxproj | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'tools/render-test/render-test.vcxproj')

diff --git a/tools/render-test/render-test.vcxproj b/tools/render-test/render-test.vcxproj
index dfe610681..94af429e8 100644
--- a/tools/render-test/render-test.vcxproj
+++ b/tools/render-test/render-test.vcxproj
@@ -164,6 +164,11 @@
     <ClInclude Include="slang-support.h" />
     <ClInclude Include="window.h" />
   </ItemGroup>
+  <ItemGroup>
+    <ProjectReference Include="..\..\source\slang\slang.vcxproj">
+      <Project>{db00da62-0533-4afd-b59f-a67d5b3a0808}</Project>
+    </ProjectReference>
+  </ItemGroup>
   <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
   <ImportGroup Label="ExtensionTargets">
   </ImportGroup>
-- 
cgit v1.2.3