Re: [Q] Compiling CommonC++ against Win2K SDK

[David Sugar]

I presume you are referring to the older Common C++ "1" series, as the 
"2" releases have not yet reached 1.3 (the latest release is 1.2.5 of 
commoncpp2).

In the "2" library releases, we no longer use the Interlock methods, I 
think partially for this reason, except for the atomic_t.  The "2" 
release also includes vsproj files for vs.net along with .dsp files for vs6.


Robert Oaks wrote:
> Disregard my message for help. I thought that this was
> a subscribing type list. But I do have a question.
>
> I am using an older version of Commonc++ (1.3.3). The Visual
> Studio 6 out of the box compiles at a WINVER = 0x400. I needed some
> of the new API's for dual monitors, so I went out and got
> the MS Win 2000 SDK (which are new libs, and includes). The new SDK
> defines WINVER = 0x0501, which makes linking fail with unresolves for
> all of the InterlockedXXX functions that are being using for resource
> locking.
>
> I have checked all (in my belief) where the problem would be. The new libs
> (kernel32.lib)
> have all Interlocked functions defined. They are also in the DLL.
>
> Can you be of assistance? I hope that it is a small problem.
>
> BTW: has this ever been compiled on the .NET suite? Cause I can not compile
> it there
> either.
>
> Robert Oaks
> Arcata Associates
> Senior Software Engineer
> RF&ESS
> (661) 276-5433
>
> Robert Oaks
> Arcata Associates
> Senior Software Engineer
> RF&ESS
> (661) 276-5433
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp