On Sun, Jun 7, 2009 at 9:07 AM, Nathan Paul
<nathanjpaul@gmail.com> wrote:
LNK4099 is described at http://msdn.microsoft.com/en-us/library/b7whw3f3.aspx. It's bad because it means the object is linked as if there is no debug information. To make this warning go away, the PDB files would have to be in the linker's search path, but I don't know how to tell the linker that information.
Nathan
On Thu, 04 Jun 2009 01:18:46 -0500, Vladimir Prus <
ghost@cs.msu.su> wrote:
On Saturday 30 May 2009 22:12:36 Nathan Paul wrote:
Hi all,
I have a prebuilt shared library built with the /Zi option using msvc. This
generates two PDB files. I setup the library in the site-config.jam file as
follows:
lib mylib
: # No dependencies
: <variant>debug:<file>$(MYLIB_DEBUG_LIB)/libmylib.lib
<variant>release:<file>$(MYLIB_RELEASE_LIB)/libmylib.lib
: # No default build
: <include>$(MYLIB_INCLUDE)
;
When I build my project using this library I get linker warnings LNK4099.
I'd like to be able to tell the linker about the location of the PDB files,
but I don't know how. Although I can rebuild the prebuilt library with the
/Z7 option instead of /Zi, I'd like to avoid it.
I miss some context here. What is linker warning 4099, what does it say, why
is it bad, and, most importantly -- what options to the linker should be
passed to make this warning go away?
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/