D.J. Heap wrote:
> I've built with the new VS2005, but it required some tweaks and since
> I'm probably not going to have time to work on them for a few weeks I
> thought I'd post a quick summary in case people start asking about it.
> The 1st issue is minor but annoying -- the new compiler spits out a
> million warnings due to the deprecation of lots of C functions (can be
> suppressed with a define as indicated below):
> .\threadproc\win32\proc.c(353) : warning C4996: 'getenv' was declared deprecated
> C:\VS2005\VC\include\stdlib.h(483) : see declaration of 'getenv'
> Message: 'This function or variable may be unsafe. Consider
> using _dupenv_s instead. To disable deprecation, use
> _CRT_SECURE_NO_DEPRECATE. See online help for details.'
Aargh! So now #*$@^*&! Microsoft is "deprecating" ISO-C standard
functions, the fscking bastards.
> The 2nd issue is zlib123 -- the new ML doesn't like the assembly
> version (tweaking build_zlib.bat or the generator to not use the
> assembly version works fine):
> inffas32.asm(594) : error A2070: invalid instruction operands
> inffas32.asm(596) : error A2070: invalid instruction operands
> inffas32.asm(610) : error A2070: invalid instruction operands
> inffas32.asm(667) : error A2070: invalid instruction operands
There's not much to be done here, except figuring out what's wrong with
the syntax and posting a patch to the zlib folks.
> The 3rd issue is linking with neon -- the new VS has 'changed' how
> external makefile projects work -- they are no longer automatically
> linked even if specified as a project dependency. libneon(D).lib has
> to be explicitly specified in the linker inputs for the relevant
> projects now.
> The 4th issue is that one of the stats tests is failing -- it seems to
> be due to a change in how wildcards on the commandline are handled,
> but I haven't looked at it very closely yet. It does not seem to be
> an actual problem with any code, just the test, at first glance.
> Other than those build/test issues, it has worked fine so far.
O.K. So it seems we'll be able to move to a recent version of VS.NET for
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Nov 6 19:44:25 2005