> -----Message d'origine----- > De : fpc-devel-boun...@lists.freepascal.org [mailto:fpc-devel- > boun...@lists.freepascal.org] De la part de Bernd Mueller > Envoyé : lundi 30 mai 2011 11:38 > À : FPC developers' list > Objet : Re: [fpc-devel] test suite, problem with missing libraries on the > target > > Jonas Maebe wrote: > > > > On 30 May 2011, at 11:19, Bernd Mueller wrote: > > > >> Jonas Maebe wrote: > >>> Why do you limit it to Linux targets? > >> > >> I am not sure about the other targets. > >> > >> LibraryFileName:= 'lib' + > >> ForceExtension(SplitFileName(PPFile[current]), 'so'); > >> > >> The above code builds the library name out of the test program name. > >> For example "Test1.pp" becomes "libTest1.so". This cannot be right for > >> a Windows target for example. > > > > Windows is not supported as a remote target, but it's indeed not correct > > for all unix targets either. The prefix of a library is always "lib" on > > all targets, afaik. The suffix is available via dynlibs.SharedSuffix. > > The downside of using the dynlibs unit is that it makes the dotest > > program dependent on libdl (and hence libc) on Linux-targets. I'm not > > sure about how to best solve this... > > One could work with a default suffix ".so" and make this overridable by > a new test option for example TEST_LIBRARY_SUFFIX.
Just add a LibExt constant to dotest.pp source with the same conditionals as for ExeExt, this should be enough. Pierre Muller _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
