Boost logo

Boost-Build :

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-04-18 04:32:09

Mat Marcus wrote:
> Why is the better than Rene's suggestion to put:
> toolset.add-requirements
> <toolset>gcc-4.2.0:<target-os>cygwin
> <toolset>gcc-4.2.0:<threadapi>pthread ;
> into user-config.jam?

It is not better, it is different. It reflects your expectation, that
despite you are building from cmd, you expect the resulting exe
linked against cygwindll.

>> I still do not recommend to use msvc compiled bjam from bash.
> Bash is my shell. It is essential to my workflows. In fact, I find
> windows unusable without it :-). Msvc is one of the compilers that I
> must support. I must also ensure that users of my libraries can build
> from the CMD shell.

Perhaps you misunderstood me? I ma in no way against using bash! (I like
it too :-) WHat I said is just: If on bash, use bjam compiled for cygwin.

> I argue that it is a bug if a build system cannot produce the same
> artifacts for a user's chosen toolset under the user's chosen shell,
> or if the artifacts on a single machine depend on how the built tool
> itself was compiled.

Let me take this to an extreme: If on linux bash would you expect the
default being cygwin targets? This essentially is what you are requesting.

And don't say linux is a different matter. I have managed, (but
currently do not use) having linux run side by side with windows
(colinux can do that).

>> This is mainly because the default setting of the target-os is not
>> correct, but also because bjam will not try to locate user-config.jam
>> from your cygwin home directory.
> Sure it will. Simply set %HOME% to the cygwin home dir. See page
> 37 of the boost build userman.pdf. I use C:\home.

Yes sure it will. I just said: You are asking for trouble, trust me.
(Or not, it is up to yours, diregarding my recommendations.)

  _  _  | Roland Schwarz
 |_)(_  | aka. speedsnail
 | \__) | mailto:roland.schwarz_at_[hidden]

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at