ivansafrin/Polycode — pull request #116 by dannywarren (2012-06-19 23:22:13+00:00)
Title: Improvements to win32 c++ template

* See individual commits for details

* Basically, my goal here was to separate out the project configuration settings required to build a polycode application, so that it would be much quicker to get up and running with a fresh visual studio project

* So, there is now a "Polycode.props" property sheet file that can be dropped in to a fresh project that includes all common polycode build defaults

* After that, you only have to:

1) Change the "PolycodeDir" variable to point to wherever you unpacked polycode to (I would like to make this more clever so that this step is not needed, as it requires enabling "expert" settings in visual studio express to get at the property sheet)

2) Add either "$(PolycodeLibsDebug)" or "$(PolycodeLibsRelease)" to the Linker/Inputs section to automatically include every static library needed by polycode

* In addition, a small post-build event will copy "defaults.pak", "hdr.pak" and the Debug/Release appropriate dll files in to the project. Users who want override these can just replace them and they won't copy over again, but it should cut down on "why aren't ScreenLabels showing up" type questions.