Boost logo

Boost-Build :

From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-06-12 13:41:34


I have an implementation for resource-only DLL support in msvc.jam. However,
I am not happy with this, especially now that I am looking at adding support for
monitoring PDB files.

The problem is that I have a rule msvc.link.resource-dll that is *exactly* the
same as msvc.link.dll, so that I can have the following generators:

generators.register-linker msvc.link.dll :
   OBJ SEARCHED_LIB STATIC_LIB IMPORT_LIB : SHARED_LIB IMPORT_LIB :
   <toolset>msvc ;
generators.register-linker msvc.link.resource-dll :
   OBJ SEARCHED_LIB STATIC_LIB IMPORT_LIB : SHARED_LIB :
   <toolset>msvc <resource-only>yes ;
generators.override msvc.link.resource-dll : msvc.link.dll ;

The difference being that a resource-only DLL does not produce a LIB
file.

The PDB situation is an extension of this, but is slightly more complex in
that the PDB output is dependant on the <debug-store>database flag.
NOTE: If we don't specify the PDB location (it will be in the same place
as the DLL/EXE), we can get away with making PDB output optionally
dependant. That is, the output is optional (so that it doesn't get copied
by the install rule and won't generate an error), but dependant on a
feature. So that would result in something like:

generators.register-linker msvc.link.dll
  : OBJ SEARCHED_LIB STATIC_LIB IMPORT_LIB
  : SHARED_LIB
    IMPORT_LIB/<resource-only>no
    PDB_FILE/<debug-symbols>on/<debug-store>database
  : <toolset>msvc ;

Thoughts?

- Reece
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/


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