Re: [Boost-users] MSVC Afx Libs incompatibility ?

From: joel szymanski (joel.szymanski_at_[hidden])
Date: 2005-11-09 19:48:20

Ok, As you make me believe that a solution exist, I test my code further and 
find that moving boost #include over microsoft Vc7.1 define (generated by 
MFC code assistant) :

#ifdef _DEBUG
#define new DEBUG_NEW
#endif

solved my problem.

Thank you for your reply,

Joel

----- Original Message ----- 
From: "Cory Nelson" <phrosty_at_[hidden]>
Newsgroups: gmane.comp.lib.boost.user
Sent: Wednesday, November 09, 2005 10:43 PM
Subject: Re: MSVC Afx Libs incompatibility ?

On 11/9/05, Jeff Flinn <TriumphSprint2000_at_[hidden]> wrote:
>
> "joel" <joel.szymanski_at_[hidden]> wrote in message
> news:dkrfot$d8c$1_at_sea.gmane.org...
> >I have just "demo_xml" serialisation test with "StdAfx.h" precompilated
> >header.
>
> Not sure what you mean here. Did you add '#include "stdafx.h"' to the
> demo_xml.cpp?
>
> > VC7.1 reply :
> >
> > nafxcwd.lib(afxmem.obj) : error LNK2005: "void * __cdecl operator
> > new(unsigned int)" (??2_at_YAPAXI@Z) déjà défini(e) dans
> > libcpmtd.lib(newop.obj)
>
> Sounds like you're linking inconsistent versions of the libs.
>
> >
> > It seems that boost libs is defining new operator as nafxcwd.lib from
> > microsoft.
> >
> > Does anyone succeed to use boost libs with "stdafx" libs ?

> I've not heard of stdafx libs, but yes many people succesfully use boost
> libs with VC7.1 win32, and MFC applications.

I think he means precompiled headers, and yes I use them quite often with 
Boost.

> Jeff Flinn
>
>
>
>
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
>
>

--
Cory Nelson
http://www.int64.org