Re: [Boost-bugs] [Boost C++ Libraries] #2181: Boost build issue on Windows/MinGW

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2181: Boost build issue on Windows/MinGW
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2009-03-02 02:42:59

#2181: Boost build issue on Windows/MinGW
  Reporter: tristen_e_at_[hidden] | Owner: vladimir_prus
      Type: Feature Requests | Status: new
 Milestone: Boost 1.36.0 | Component: build
   Version: Boost 1.35.0 | Severity: Problem
Resolution: | Keywords: win32 gcc static link mingw

Comment(by tristen_e_at_[hidden]):

 Hi Vlad,

 Sorry to take so long in responding - I only just found the email.

 To answer your question: I'm as confused as you. I politely asked GCC to
 link statically to the boost libs; linking completes successfully (ie:
 with no errors); it's only at run-time that the executable complains
 rather rudely about not being able to find the boost dlls.

 Since I typed the issue in all those months ago I think the problem is
 more related to the fact that I'm using MinGW in a Cygwin environment.
 Hence maybe that's why the linker in my environment is treating .lib files
 as if they were .dll files.

 So whatever the reason, renaming the .lib files to .a files works, ie: the
 compiler/linker makes an executable statically linked using the .a files.

 And finally, if my suspicions are correct, then this isn't a problem at
 all, ie: how can bjam know if my intentions are to use the Windows boost
 libraries from Cygwin, unless of course you guys are willing to add a
 --toolset=mingw-via-cygwin flag to bjam ;)

 No I wouldn't either :)

Ticket URL: <>
Boost C++ Libraries <>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:59 UTC