Trouble building Syzygy in VS

[Jeff Wilson]

Hi all,

I want to build syzygy in MS VS 2010 Ultimate on a Win 7 64-bit OS. Unfortunately, there are some issues with the build. Here are 3 build errors that I managed to find a workaround for:

1. pcre_lib warning treated as error => Proj > Properties > C/C++ > Treat Warnings As Errors : No

2. test_dll error LNK2005: new and delete already defined in LIBCMTD.lib => Proj > Properties > Linker > Input : add "Nafxcwd.lib;Libcmt.lib;" to Ignore Specific Default Libraries

3. agent_common_lib Error C2712 => Proj > Properties > C/C++ > Code Generation > Enable C++ Exceptions > Compile without /EHsc

However, now I ran into about 200 LNK2001 and LNK2019 "unresolved external symbol" errors. Here are just a couple of them

Error 8 error LNK2019: unresolved external symbol "public: struct _IMAGE_NT_HEADERS * __thiscall base::win::PEImage::GetNTHeaders(void)const " (?GetNTHeaders@PEImage@win@base@@QBEPAU_IMAGE_NT_HEADERS@@XZ) referenced in function "private: bool __thiscall agent::coverage::Coverage::InitializeCoverageData(void *,struct common::IndexedFrequencyData *)" (?InitializeCoverageData@Coverage@coverage@agent@@AAE_NPAXPAUIndexedFrequencyData@common@@@Z) D:\cygwin64\home\l2\Syzygy\src\syzygy\agent\coverage\coverage.obj coverage_client

Error 9 error LNK2001: unresolved external symbol "public: struct _IMAGE_NT_HEADERS * __thiscall base::win::PEImage::GetNTHeaders(void)const " (?GetNTHeaders@PEImage@win@base@@QBEPAU_IMAGE_NT_HEADERS@@XZ) D:\cygwin64\home\l2\Syzygy\src\syzygy\agent\coverage\agent_common_lib.lib(process_utils.obj) coverage_client

Does anyone have any suggestion on how to fix these errors? 

Any help would be appreciated.

Thanks,

Jeff

[Sigurður Ásgeirsson]

Hi Jeff,

the Syzygy tip-of-tree should never be broken. You're presumably using depot tools to pull your workspace together? This should ensure that all the third party sources are of consistent versions.

Generally when we see this class of problems in the build, it's because of something like syncing without rebuilding the solutions, or due to stale libraries and objects hanging around in the build dir.

Have you tried doing a clean build from scratch?

Note that a clean build in Visual Studio doesn't actually remove all artifacts, so it's better to just nuke and pave the output directories in /src/build/Debug|Release.

Good luck,

Siggi

--
You received this message because you are subscribed to the Google Groups "sawbuck-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sawbuck-user...@googlegroups.com.
To post to this group, send email to sawbuc...@googlegroups.com.
Visit this group at http://groups.google.com/group/sawbuck-users.
For more options, visit https://groups.google.com/groups/opt_out.