From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-03-21 07:03:56
David Abrahams wrote:
> Vladimir Prus <ghost_at_[hidden]> writes:
> >> I don't know if it is common, but it is a workaround that I have used.
> >> It will work on Windows/GCC, but I assume you mean will it work on
> >> MSVC. On MSVC, you will have to provide a ".def" file with "EXPORT"
> >> statements and I'm not sure if there is a standard automatic way to
> >> create this file. But we can cross this bridge when we come to it.
> > Okay. I think I've closed achive creating problem already. Need to
> > address DLLs in future.
> Oh, I wanted to point out that the usual way to deal with this is to
> use response files. Only GCC is immune to that approach, it seems.
Oh... I forgot it completely :-( Then, the trick will be needed for gcc only,
which does not require __declspec(export) to export staff. Good.
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