Actually, its an STL issue. The stock STL shipped with visual studio has,
lets just call them "issues" with thread safety ;). So, we use the sgi STL
for windows builds, which you can snag at
All the freeamp projects have the NOMINMAX define, hence the min max issues
when building with the microsoft stl.
----- Original Message -----
From: Gary R. Van Sickle <[EMAIL PROTECTED]>
Sent: Friday, September 15, 2000 11:32 PM
Subject: min()/max() problems with MSVC6.0

> Hi guys,
> 1.  Freeamp rocks, and I thank each and every one of you who has worked on
> it.  Give me Free Software, or give me Death!
> 2.  I've been building from cvs, using MSVC 6.0, and while it compiles and
> runs perfectly (well, let's say "as I would expect unreleased cvs code to
> run"), it chokes on every min() or max() in the project.  I have to add
> following unsightly hack under the #includes of each file using min() or
> max() to get it to compile:
> // These are Windows/MSVC6.0 specific hacks
> // to get the min() and max() macros we want.
> #define min _MIN
> #define max _MAX
> Clearly, this won't do.  Is this a known issue?  I've known about it for
> maybe the last month or so.  How do you guys do your beta builds?
> _______________________________________________


Reply via email to