Boost logo

Boost-Build :

From: levent (leventyilmaz_at_[hidden])
Date: 2007-05-30 11:24:43

Vladimir Prus wrote:
> On Tuesday 29 May 2007 20:05, Server Levent Yilmaz wrote:
>>Hi All,
>>Does anyone have a BBv2 toolset for the Portland Group C++ compiler?
>>Given the rest of my day, I probably won't be as lucky to have "yes" for an
>>answer, so moving on...
>>I really do not want much. All I need is to have bjam effectively execute
>>the following on boost source
>> $(CXX) $(CXXFLAGS) -c whatever.cpp
>> ..
>> ar rcs libname.a whatever.o
>>where CXX and CXXFLAGS are set for the PG compiler and create silly single
>>threaded static libraries on my given platform.
> I would suggest that the easiest approach would be to create a support
> module for your compiler. It's easier than you think:
> 1. Copy vacpp.jam to whateveryourlike.jam.
> 2. In that file, replace 'acc' with 'whateveryoulike'.
> 3. Look at all 'flag' lines. If the option being set is wrong, make it
> right or comment out the line.
> 4. Look at 'action' blocks, remove hardcoded options.
> That's it. The result won't be ideal (since vacpp.jam is the simplest
> toolset, not the best), but it should work.

Thanks many Volodya. It was simple enough.

Yet, there are a couple of details I wish I knew (or knew how to know
:)). Such as for example, what is the various modifiers after "actions".
For instance, what is the difference between the following two:

actions { $(LINKER) $(OPTIONS) $(NEEDLIBS) ... }


actions bind NEEDLIBS { $(LINKER) $(OPTIONS) $(NEEDLIBS) ... }

what does "bind" do?

Also, what does "updated together piecemeal" mean? Is there a fine
manual where I can dig these up?

thanks again.


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