I've done a little more testing. There are two steps I had to perform to eliminate those pesky messages. 1: Hack link.exe and patch out the 4099 code 2: Add /ignore:4099 to the link command line
On Tue, Oct 18, 2011 at 2:10 PM, Nicky Perian <nickyper...@yahoo.com> wrote: > Deliver the *pdb files with each library as is done with vorbis_static > within 3p-ogvorbis' build-cmd.sh. > > ________________________________ > From: Oz Linden (Scott Lawrence) <o...@lindenlab.com> > To: opensource-dev@lists.secondlife.com > Sent: Tuesday, October 18, 2011 10:54 AM > Subject: Re: [opensource-dev] Eliminate VS2010 LNK4099 errors > > On 2011-10-17 20:41, Jonathan Welch wrote: >> I've got tired of seeing blasts of LNK4099 errors fly up the screen >> when I compile so I looked into how to eliminate them. It seems the >> only way to do this is to hack link.exe and change the 4 bytes that >> equal 4099 to something else. See >> http://www.bottledlight.com/docs/lnk4099.html >> >> In my case this was at location 15a0. > > I don't think we're going to officially suggest doing that.... :-) >> Of course it would be nice if the files in question did not cause this >> to happen in the first place. > > Anyone know how to make that happen? > > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges > > > > _______________________________________________ > Policies and (un)subscribe information available here: > http://wiki.secondlife.com/wiki/OpenSource-Dev > Please read the policies before posting to keep unmoderated posting > privileges > _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
