From: Kirill Lapshin (klapshin_at_[hidden])
Date: 2003-10-17 12:30:18
I am facing following problem -- I need a way to specify a def file
for one of my projects. It is basically a list of functions to export
from dll, it is supplied on link phase via /def:def_file flag. It is
sometimes important to export unmangled functions for VB integration,
or other similiar tasks.
Not sure what the right solution is, probably toolset specific feature.
I am willing to invest some time in this, but not sure where to start
-- any suggestions pointers are more then welcome.
Currently as a workaround I am using path-constant to capture path to
def file, and then pass it via <linkflags> to linker.
While we are at the topic, let me ask a quick question. What is the
right way to say that given library should be built only on specific
platform and/or toolset? Ideally I would like this feature to
propagate to other targets which are using that platform specific
library. I tried to add <toolset>msvc to requirements, but end up with
some targets built with gcc while others with msvc. All peppered with
warnings that targets are not link compatible.
What I would like to see is: when gcc is used all msvc specific
targets are silently skipped (with warning probably).
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