[BBv2]some ideas

From: pal.tw (pal.tw_at_[hidden])
Date: 2003-10-17 09:33:07

Hi, all:
I add some builtin features which about the
target-platform property to BBv2.
It's very simple, and I borrow some code from the
variant rule.
Although the value of the 'target-os' feature only
contains windows-series now.
Hope it is useful and could be added to the official
version of BBv2.

Sometimes I think a few modules of the BBv2 are too
large to maintain easily.
So I don't add the code to 'builtin.jam' directly, but
to another file.
And merge them together. Maybe in the same way we can
break some modules
into smaller ones according to their objectives and
dependency.
The naming convention of the files is adopted from the
suggestion of
Rational Software Corporation.

MFC, stlport, boost libraries, and wxWindows -- my
favorite GUI framework,
are so popular and common. Maybe The libraries like
these should be
configured individually like toolsets but classified
in another category.

Composite features can be expanded into any other
features
including other composite features. But I found the
composite feature
would not expand correctly to the exist feature
<library>.
Like this...
------------------------------------------------------------------------------------
composite target-os : Win95&NT : Win32 :
<define>WINVER=0x0400 <define>_WIN32_DCOM
<library>/System//unicows ;
------------------------------------------------------------------------------------
So I rewrite that to
------------------------------------------------------------------------------------
composite target-os : Win95&NT : Win32 :
<define>WINVER=0x0400 <define>_WIN32_DCOM
<library-file>unicows.lib ;
------------------------------------------------------------------------------------

Is something wrong within the process of the expansion
?

Another issue...
Basically the new OS will be back-compatiable with the
old ones as possible.
The value of 'target-os' is 'Win95' means the program
or module
can run in the OS newer than 'Windows 95'.
It seems that the feature should be link-incompatible,
but it is not exact.

Because the target with <targe-os>Win98 could link
with
the library with <targe-os>Win95 requirment, but the
target
with <targe-os>Win95 should not link with the library
with <targe-os>Win98.
Or it will make the program not run in Windows 95
indeed.

Maybe we should consider the relationship of the
values of the same feature,
especially they are owned with different targets which
will be linked together.

-----------------------------------------------------------------
¨C¤Ñ³£ Yahoo!©_¼¯
®üªºÃC¦â¡B­·ªº®ð®§¡B·R§Aªº·Å«×¡AºÉ¦b«H¯È©³¹Ï
http://tw.promo.yahoo.com/mail_premium/stationery.html --0-1307944425-1066401187=:5057 Content-Type: application/x-zip-compressed; name="BBv2addin.zip"
Content-Transfer-Encoding: base64
Content-Description: BBv2addin.zip
Content-Disposition: attachment; filename="BBv2addin.zip"

[Attachment content not displayed.] --0-1307944425-1066401187=:5057--