>There's been talk about addressing this (see bugzilla), but I don't know
if
>it's been done yet. If you're building a VC++ static library, both of the
>PLATFORM_... macros should expand to nothing:
>
>#define PLATFORM_EXPORT
>#define PLATFORM_IMPORT
>
The pointer to the thread is here:
"http://
rom: Martin Bosticky [mailto:mbosticky@;aimltd.co.uk]
Sent: Friday, October 25, 2002 5:22 AM
To: [EMAIL PROTECTED]
Subject: RE: compiling xerces into a static library
Thanks for the comments. I would suspect that they probably suppress the
warning as you said but somehow I have not duplicated that i
his already?
Martin Bosticky
Software Engineer
Action Information Management Ltd.
Tel: (01225) 711200
Fax: (01225) 711222
Email: [EMAIL PROTECTED]
-Original Message-
From: Jesse Pelton [mailto:jsp@;PKC.com]
Sent: 24 October 2002 19:31
To: '[EMAIL PROTECTED]'
Subject: RE: c
ltd.co.uk]
Sent: Thursday, October 24, 2002 9:19 AM
To: [EMAIL PROTECTED]
Subject: compiling xerces into a static library
Hi.
I have compiled xerces into a static library on VC6 since I wanted to
add an XML parser but didn't want to carry the distribution overhead
needs
Is such practice
ld be surprised if it didn't, unless the stock makefile suppresses
the warning with /wd4355.
-Original Message-
From: Mark Weaver [mailto:mark@;npsl.co.uk]
Sent: Thursday, October 24, 2002 2:20 PM
To: [EMAIL PROTECTED]
Subject: RE: compiling xerces into a static library
#pragma warnin
C.com]
> Sent: 24 October 2002 18:45
> To: '[EMAIL PROTECTED]'
> Subject: RE: compiling xerces into a static library
>
>
> I build a static Xerces library using VC 7. (Did it with VC 6, too, but
> we've moved on.) I haven't encountered any problems. I haven
Hi.
I have compiled xerces into a static library on VC6 since I wanted to
add an XML parser but didn't want to carry the distribution overhead
needs
Is such practice discouraged? I nave noticed I got extra 8 warnings when
compiling it and well, I am not sure if that would make the library
unstabl
