Rene Rivera writes:
You have to be carefull when changing the name. As the variant names for build+install require the toolset names to be in a perticular form. So you either update the common-variant-tag rule to account for your changes. Or you need to follow some rules:
* You can use the short name or the long name of the toolset. For example you can use either "intel-win32" or "iw".
OK, let's go with "iw", then.
* You need the version of the toolset to include both major and minor numbers separated by a period. No need for patch numbers. So here you have to keep the "7.1".
OK.
* 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?
* 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: switch $(toolset) { case borland* : toolset-tag += bcb ; case como* : toolset-tag += como ; case cwpro8* : toolset-tag += cw 8 ; case cwpro9* : toolset-tag += cw 9 ; case darwin* : toolset-tag += ; case edg* : toolset-tag += edg ; case gcc* : toolset-tag += gcc ; case intel-linux* : toolset-tag += il ; case intel-win32* : toolset-tag += iw ; ... ?
You can probably shorted "vc6" to just "6", assuming that VC is the only supported backend for the toolset.
So the shortest I would suggest is:
iw-7.1-6-stlport453-tools.jam
Which comes in at 29 chars. You could even add back in the "vc" and still be at 31 chars :-)
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? Thanks for the assistance, -- Aleksey Gurtovoy MetaCommunications Engineering