Re: [Boost-users] STL-PORT and VC 7.1

From: Sliwa, Przemyslaw (London) (Przemyslaw_Sliwa_at_[hidden])
Date: 2006-01-23 05:41:19

This what I did. 
I had to create the projects from scratch. Fairly simple. 
Most of the test compile and link fine. Some of them fail.

Thanks for help to anyone,

Pshemek

Kind regards

Pshemek 

 

Przemyslaw Sliwa 
Global Foreign Exchange 

FX Risk Engine Development
Merrill Lynch 
(   [phone] 
)         +44  (0)79 6325 2319
*   Email: przemyslaw_sliwa_at_[hidden]

-----Original Message-----
From: boost-users-bounces_at_[hidden]
[mailto:boost-users-bounces_at_[hidden]] On Behalf Of Nat Goodspeed
Sent: 20 January 2006 15:57
To: boost-users_at_[hidden]
Subject: Re: [Boost-users] STL-PORT and VC 7.1

> -----Original Message-----
> From: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] On Behalf Of Sliwa, Przemyslaw (London)
> Sent: Friday, January 20, 2006 10:32 AM
> To: boost-users_at_[hidden]
> Subject: Re: [Boost-users] STL-PORT and VC 7.1
> 
> I have a quick question - I would like to build the static library and
> not the DLL.
> Could you tell me what should be changed in the project apart form the
> "General->static lib"?

[Nat] Um, no. But since .vcproj files are specially-formatted text
files, I assume the worst case would involve building a new
static-library project by manually setting things the same way in your
new project file as in my old one. The IDE may let you change the root
type of a project after the fact; I've never tried.
 
> Do you know how to disable the auto-link of boost?

[Nat] These are things we changed in boost/boost/config/user.hpp:

// BOOST_WHATEVER_DYN_LINK: Forces library "whatever" to be linked as a
dll 
// rather than a static library on Microsoft Windows: replace the
WHATEVER 
// part of the macro name with the name of the library that you want to 
// dynamically link to, for example use BOOST_DATE_TIME_DYN_LINK or 
// BOOST_REGEX_DYN_LINK etc (this macro is used to turn on
__declspec(dllimport) 
// modifiers, so that the compiler knows which symbols to look for in a
dll 
// rather than in a static library).  
// Note that there may be some libraries that can only be statically
linked 
// (Boost.Test for example) and others which may only be dynamically
linked 
// (Boost.Threads for example), in these cases this macro is
unsupported.
// #define BOOST_WHATEVER_DYN_LINK
#define BOOST_FILESYSTEM_DYN_LINK
#define BOOST_SIGNALS_DYN_LINK
#define BOOST_PYTHON_DYN_LINK
 
// BOOST_ALL_NO_LIB: Tells the config system not to automatically select

// which libraries to link against.  
// Normally if a compiler supports #pragma lib, then the correct library

// build variant will be automatically selected and linked against, 
// simply by the act of including one of that library's headers.  
// This macro turns that feature off.
#define BOOST_ALL_NO_LIB

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

If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------