Re: [Boost-users] [python] Linker error when initializing numpy

Subject: Re: [Boost-users] [python] Linker error when initializing numpy
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2017-11-18 10:08:08

From: Boost-users [mailto:boost-users-bounces_at_[hidden]] On Behalf Of degski via Boost-users
Sent: 17 November 2017 21:33
To: boost-users_at_[hidden]
Cc: degski
Subject: Re: [Boost-users] [python] Linker error when initializing numpy

 

On 17 November 2017 at 09:16, Christian Henning via Boost-users <boost-users_at_[hidden]> wrote:

Ø  It seems that linking to static boost libs is not supported on Windows with Visual Studio 2017. Not sure why?

 

Ø  This is not the case, linking to static libs works just fine.

 

But the static libraries are not created by default.

 

Personally I think that this is not ideal.

 

But as the number of libraries has increased, so the build time has become so long that doubling it to do static as well as shared/dynamic is a bit much.

 

(Personally, I find I only need to generate a small subset of ‘system’n’test’ libraries).

 

Perhaps we could we have a switch to the default b2 command after bootstrap that would do this?

 

I’d prefer to see at least a set of example command files that create both shared/dynamic and static libraries.

 

And a warning output that the default b2 will only create shared/dynamic libraries and a link on how to create the static ones.

 

This has caused a long stream of questions on various lists.

 

Paul

 

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]