Subject: Re: [boost] [testing] Add a tester with hidden visibility
From: Robert Ramey (ramey_at_[hidden])
Date: 2015-05-08 18:49:39
Andrey Semashev-2 wrote
> On Friday 08 May 2015 08:21:58 Robert Ramey wrote:
>> Andrey Semashev-2 wrote
>> > On Thursday 07 May 2015 09:22:26 Robert Ramey wrote:
>> >> The original question suggested that if a tester changed the jam file
>> >> that the switch gcc visibility=hidden was enabled then tests would
>> > I did not suggest that the tests would immediately pass. But I would
>> > to
>> > have such tester - for users to see which libraries have problems, and
>> > library maintainers to be able to fix those problems.
>> If the jam file includes the visibility=hidden switch then ALL the
>> 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
I don't think this is disputable.
Furthermore, once one makes any required changes to support gcc
I don't think there is any scenario for which one would not want to use it.
the best solution would be to added to the jam file whenever it's supported.
-- View this message in context: http://boost.2283326.n4.nabble.com/testing-Add-a-tester-with-hidden-visibility-tp4675242p4675328.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk