Subject: Re: [boost] [testing] Add a tester with hidden visibility
From: Robert Ramey (ramey_at_[hidden])
Date: 2015-05-09 11:19:01
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
>> by default.
> How a flag added for a single toolset on a single tester would affect all
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
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
it's supported. There is no scenario under which adding it to project.jam
would be beneficial.
-- View this message in context: http://boost.2283326.n4.nabble.com/testing-Add-a-tester-with-hidden-visibility-tp4675242p4675333.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