Re: Extended lib rule

From: hf_pabst (hfp_at_[hidden])
Date: 2005-06-27 15:01:25

> Yes, and it's pretty easy for a DLL author to set up. I am not
> convinced that the build system should be doing this automatically.
> There are, after all, plugin DLLs that hardly export anything (like
> Python extension modules).

Thats right. It's nice to have an out-of-the-box working code -- with 
any build system. On the other side each build system can support 
some defines.

I know the common solution with a top-level header, but this seems a 
nice place to discuss this. Boost.Build V2 is a nice build system and 
it's not only for use in a single direction -- it can also influence 
coding standards. Each boost library has this ability (for me).

Many windows users doesn't understand dynamic link libraries (i'm 
teaching something linke this for many beginner). We can simply 
establish (and document) a standard. Unique project names make sense 
for unique defines -- the code will then reflect the name of the 
project...

class LIBMYPROJECT anything {
...
};

Many Thanks for your answers,
Hans.