You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the VS2008 solution (and possibly others) a minimum of Windows SDK v7 is required. This manifests itself as failure to find VER_SUITE_WH_SERVER when building. In my case changing the VS2008 from v6 to v7 solved the problem
WTL seems to be a pre-requisite for building. I couldn't find this mentioned in the documentation, but maybe I missed it.
The project and/or solution files mention the $platform and $configuration macros, these should be $platformname and $configurationname otherwise the various build overwrite each other
When building for, say, DEBUG, the client code links against zlibSD.lib but the zlib build only produces zlib.lib. Changing the output name approriately for a given build solved this.
It could be that I'm being naive about the above issues, but it seems as though building using CI scripting doesn't guarantee that the IDE builds will work without tweaking. :-(
The text was updated successfully, but these errors were encountered:
I think you have the right picture @colindavidfoster . The CI server scripted build takes precedence over a straight shot F5 build from Visual Studio.
If you'd like to make some changes to make it easier to build from Visual Studio that does not compromise CI server's build integrity I think the community would be open to those kinds of changes.
I think we would prefer any changes to be minimal in nature, if at all possible.
OK I'll see what I can come up with. I'll probably take is slow as all my Git work so far has been in house. Contributing to an external project will be a new experience
When building the VS2008 solution (and possibly others) a minimum of Windows SDK v7 is required. This manifests itself as failure to find VER_SUITE_WH_SERVER when building. In my case changing the VS2008 from v6 to v7 solved the problem
WTL seems to be a pre-requisite for building. I couldn't find this mentioned in the documentation, but maybe I missed it.
The project and/or solution files mention the $platform and $configuration macros, these should be $platformname and $configurationname otherwise the various build overwrite each other
When building for, say, DEBUG, the client code links against zlibSD.lib but the zlib build only produces zlib.lib. Changing the output name approriately for a given build solved this.
It could be that I'm being naive about the above issues, but it seems as though building using CI scripting doesn't guarantee that the IDE builds will work without tweaking. :-(
The text was updated successfully, but these errors were encountered: