Build/WinLink4099 - Revision history

Dave at 18:37, 14 February 2012

2012-02-14T18:37:37Z

← Older revision		Revision as of 18:37, 14 February 2012
Line 12:		Line 12:
	Now, you could probably live with it if there was just one warning per-library and you don't really care about compiling with 0 warnings, but it's typically hundreds of warnings, and we all know how slow VC80 gets when you spam the output window. So, no sanctioned workaround, let's do this the hard way [4]. You could go after the code that generates a 4099 and prevent it from ever getting generated, or the code that prevents it from being ignored. The latter seems easier, since they have a whole list of items it'll probably be in a table.		Now, you could probably live with it if there was just one warning per-library and you don't really care about compiling with 0 warnings, but it's typically hundreds of warnings, and we all know how slow VC80 gets when you spam the output window. So, no sanctioned workaround, let's do this the hard way [4]. You could go after the code that generates a 4099 and prevent it from ever getting generated, or the code that prevents it from being ignored. The latter seems easier, since they have a whole list of items it'll probably be in a table.

	Fire up your favorite hex editor on link.exe (likely the one in "C:\Program Files\Microsoft Visual Studio 8\VC\bin") and look for 4099 at 32 bits wide. The very first hit also ~~has~~ 4088 before it, and 4105 after it, bingo! I set it to 65535; pick your poison, but you probably want to avoid the 4xxx range. Hooray for no more annoying PDB warnings, at least until the next VS SP or VC9.		Fire up your favorite hex editor on link.exe (likely the one in "C:\Program Files\Microsoft Visual Studio 8\VC\bin") and look for the first occurrence of 4099 at 32 bits wide (03100000). The '''very first hit''' will also have 4088 before it, and 4105 after it, (see hex below) bingo! I set it to 65535 (FFFF0000); pick your poison, but you probably want to avoid the 4xxx range. Hooray for no more annoying PDB warnings, at least until the next VS SP or VC9.

	http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=162246		http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=162246

Dave at 18:31, 14 February 2012

2012-02-14T18:31:10Z

← Older revision		Revision as of 18:31, 14 February 2012
Line 1:		Line 1:
	[[http://www.bottledlight.com/docs/lnk4099.html original page]]		[http://www.bottledlight.com/docs/lnk4099.html original page]

	'''Problem: Visual Studio likes to extensively warn you about missing PDB files for library files when linking.		'''Problem: Visual Studio likes to extensively warn you about missing PDB files for library files when linking.

Dave: Created page with "http://www.bottledlight.com/docs/lnk4099.html original page '''Problem: Visual Studio likes to extensively warn you about missing PDB files for library files when linking. '..."

2012-02-14T18:30:30Z

Created page with "http://www.bottledlight.com/docs/lnk4099.html original page '''Problem: Visual Studio likes to extensively warn you about missing PDB files for library files when linking. '..."

New page

[[http://www.bottledlight.com/docs/lnk4099.html original page]]

'''Problem: Visual Studio likes to extensively warn you about missing PDB files for library files when linking.
'''

warning LNK4099: PDB 'XXX' was not found with 'YYY' or at 'ZZZ'; linking object as if no debug info

You might think that it's not a big deal: recompile the library to not use PDB files, or disable the warning. The former option isn't available if it's a 3rd party SDK without source code, and the latter option isn't possible (more on that in a second).

At least in Visual Studio 2003 (7.1) and Visual Studio 2005 (8.0), 4099 is on a 'non-ignorable' warning list. This means that you can't use /ignore in the linker command line options to get rid of it. Brilliant! This is by design [1] and they don't care enough to provide any other mechanism right now [2]. To be fair, both the /ignore switch and which warnings are non-ignorable seem to be undocumented, but someone else has made a handy list of them [3].

Now, you could probably live with it if there was just one warning per-library and you don't really care about compiling with 0 warnings, but it's typically hundreds of warnings, and we all know how slow VC80 gets when you spam the output window. So, no sanctioned workaround, let's do this the hard way [4]. You could go after the code that generates a 4099 and prevent it from ever getting generated, or the code that prevents it from being ignored. The latter seems easier, since they have a whole list of items it'll probably be in a table.

Fire up your favorite hex editor on link.exe (likely the one in "C:\Program Files\Microsoft Visual Studio 8\VC\bin") and look for 4099 at 32 bits wide. The very first hit also has 4088 before it, and 4105 after it, bingo! I set it to 65535; pick your poison, but you probably want to avoid the 4xxx range. Hooray for no more annoying PDB warnings, at least until the next VS SP or VC9.

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=162246
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=176188
http://members.ozemail.com.au/~geoffch/samples/programming/msvc/link/link/options/ignore.htm

Yes, I really am proposing that you patch your linker to ensure a clean build. If it helps you sleep at night, think of it as correcting a profoundly stupid oversight by Microsoft. There just isn't any other solution if you want to compile in debug mode without getting vendors to recompile their libraries.

The usual caveats apply when modifying executables (Make a backup copy, validate what you're attempting to change, no warranty express or implied, etc...). If you have a newer or older link.exe, the list of unignorable warnings may be different, or stored differently, so verify that the value you're replacing is sane:

... F8 0F 00 00 - 03 10 00 00 - 09 10 00 00 ... (4088, 4099, 4105)

'''Copyright (C) 2007 Michael Noland. All rights reserved.'''