From: David Abrahams (dave_at_[hidden])
Date: 2005-04-06 08:05:18
"Thomas Schipolowski" <thomas.schipolowski_at_[hidden]> writes:
>> Works fine for me here, building and testing with Boost.Build. This
>> is a build problem on your end
> Yes, I compiled the test case with BJam and now it works flawlessly. Great!
> One complication is left: I wonder now how to explain to BJam that some of
> my files need to be fed to a fortran compiler, before they are linked with
> the c++ objects. Would you say that using BJams 'prebuilt binaries' feature
> with an external fortran build is the best way to achieve that, or is it
> reasonably easy to tell BJam about the fortran toolchain? Is the latter
> documented somewhere?
Well, Boost.Build v2 has a fortran toolset, but it seems to be under-documented
$ bjam --v2 --help fortran
This file contains common settings for all fortran tools
Module 'fortran' classes:
Use --help fortran.<class-name> to get more information.
I'm not sure what you need to do to configure it. Maybe its author
can help? I suggest following up to the jamboost list
> Again, thanks very much for the quick help.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk