Aleksey Gurtovoy wrote:
Rene Rivera writes:
* You need to keep "stlport" in the name. [This would be an easy one to change to recognize a shorter synonym]
Can we have "stlp" as a synonym, then?
Sure... I'll make the change.
* You need to keep the basic format of: <name>-<version>...stlport...-tools.jam
Even with that boost-base.jam will need to change to handle both "intel-win32" and "iw".
Here, I suppose:
case intel-linux* : toolset-tag += il ; case intel-win32* : toolset-tag += iw ;
No. The "case *" part handles the generic case of using the short "iw" name: case * : toolset-tag += [ MATCH "^([^-]*)" : $(toolset) ] ; It's this part further down in toolset::requirements rule: case intel-win32* : { # dynamic runtime only comes in the multi-threading flavor if <runtime-link>dynamic in $(properties) { requirements += <threading>multi ; } }
OK, sounds good enough. What about "como-win32-4.3.3-vc7.1-tools.jam"? Does renaming it to something like "comow-4.3.3-vc7.1-tools.jam" requires some tweaks to other parts of the Boost.Build as well?
Yes that name would work without changes. I'll make the changes now... OK done. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq