It's difficult to keep the various clang sub-toolsets up to date. As each one diverges and means we have to possibly update them all if something key changes. The sub-toolset arrangement also makes it harder to deal with targeting different OS's at the same time. As it means initializing a new toolset for each one.
Describe the solution you'd like
We should consolidate the variations into the root clang toolset and moce to using the target-os feature to account for the differences.
After #281 this is mostly done, clang-vxworks I think should be simply removed because it does nothing except strangely adds -fpic -shared -non-static at shared link step.
Describe your use case
It's difficult to keep the various clang sub-toolsets up to date. As each one diverges and means we have to possibly update them all if something key changes. The sub-toolset arrangement also makes it harder to deal with targeting different OS's at the same time. As it means initializing a new toolset for each one.
Describe the solution you'd like
We should consolidate the variations into the root clang toolset and moce to using the
target-os
feature to account for the differences.Additional context
An example of a naming confusion "issue" that also arises from the different sub-toolsets.. https://github.com/bfgroup/b2/issues/32