Andrey Semashev-2 wrote
On Friday 08 May 2015 15:49:39 Robert Ramey wrote:
Andrey Semashev-2 wrote
On Friday 08 May 2015 08:21:58 Robert Ramey wrote:
If the jam file includes the visibility=hidden switch then ALL the testers will be using it by default.
No, the flag can be added in user-config.jam, on the tester's site.
yes - if the jam file includes the flag, then ALL testers will be using it by default.
How a flag added for a single toolset on a single tester would affect all testers?
It wouldn't. My view is that : if a library can be built and used with visibility=hidden there is no reason not to build it this way, this flag should be in the Jamfile. If a library cannot be built and used with visibility=hidden there is no reason to build it this way so if visibility=hidden isn't in the Jamfile, adding for a tester is a pointless exercise. Hence, visibility=hidden should be added to the Jamfile if possible so that the library will be built and tested with visibility=hidden if and only if it's supported. There is no scenario under which adding it to project.jam would be beneficial. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/testing-Add-a-tester-with-hidden-visibili... Sent from the Boost - Dev mailing list archive at Nabble.com.