Andrey Semashev-2 wrote
On Friday 08 May 2015 08:21:58 Robert Ramey wrote:
Andrey Semashev-2 wrote
The original question suggested that if a tester changed the jam file so that the switch gcc visibility=hidden was enabled then tests would
On Thursday 07 May 2015 09:22:26 Robert Ramey wrote: pass.
I did not suggest that the tests would immediately pass. But I would like to have such tester - for users to see which libraries have problems, and for library maintainers to be able to fix those problems.
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. I don't think this is disputable. Furthermore, once one makes any required changes to support gcc visibility=hidden I don't think there is any scenario for which one would not want to use it. So the best solution would be to added to the jam file whenever it's supported. 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.