For the program I am working on, for which I do not write the source code, the list for the names of externals that should be exposed to the user is: anything starting with swe_ + 33 miscellaneous symbols.
If the ABI is extended additional symbols will probably start with swe_ It would be nice of libtool supported both -export-symbols-regex and -export-symbols. Then I could describe everything starting with swe_ using -export-symbols-regex and the miscellaneous list with -export-symbols. Unfortuantely using both leads to an error. Is there any reason the use of both could not be supported in future versions of libtools? Under the present system I have 2 choices: 1) one long list of all the symbols which will have to be updated if the ABI is extended. 2) One huge regex like this. > swe_regex='(^swe_)' > swe_regex+='|(^afl2planet$)' > swe_regex+='|(^calc$)' > > 31 other entries like this here > > swe_regex+='|(^to_mean_ekl$)' > > > libswe_la_LDFLAGS = \ > > -lm \ > -export-symbols-regex "$(swe_regex)" This probably won't have to be updated if more swe_ symbols are added, but it is ugly. What is the limit on regex size? Which is best practice? Thank You. -- Paul Elliott 1(512)837-1096 pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ https://lists.gnu.org/mailman/listinfo/libtool
