Alan W. Irwin wrote: > On 2008-09-04 08:10-0700 Rafael wrote the attached message concerning > reducing the number of symbols that are exported from our libraries. > > I brought up this issue myself a month ago, and I think that wiki > reference is worth repeating: > > "The wiki (http://gcc.gnu.org/wiki/Visibility) on visibility for > libraries > compiled by gcc, g++, etc., has just been mentioned on the CMake > list...." > > According to that wiki, the advantages of limiting symbols that are > exported > is smaller libraries and less loading latency. I would love to see that > happen so I agree with Rafael this is well worth doing. However, an > alternative implementation would be to follow the cookbook in the > above wiki > to extend what we currently do for windows in include/pldll.h to > handle the > gcc case. The obvious advantage of this approach is once > include/pldll.h is > changed it affects both current API and future API so there is some > benefit > in terms of not having to maintain an additional file such as included in > Rafael's patch whenever we add to our API. > > Thus, I lean toward the approach of modifying include/pldll.h, but I also > admit to being non-expert in this field, and there may be some practical > limitation I am missing. Therefore, I would prefer the C/C++ experts > here > to make the decision about which approach to take, and I will be happy > to go > along with whatever is decided by them. The important thing is to > clean up > our exported symbols! > Hi Alan,
from the description on the Gnu Wiki I conclude that all that is needed is two new macros to define the visibility for each function we define in the C code (I have also tried to understand the more technical description it refers to, but that is a bit above my head :)). I'd say, let's go for it: for those platforms that do not support this mechanism, we need to make them empty and for platforms that use a different syntax (e.g. Windows) we can solve that easily enough. Regards, Arjen ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel