From: Marcel R. <ru...@sw...> - 2002-04-07 20:07:51
|
Thanks for your detailed answer. The libset libs still don't show up: <echo message="TRYING: ${CORBACPP_HOME}/lib/libmico.so"/> <cc debug="true" link="executable" outfile="${testsuite.dir}/c++/bin/${exeName}" objdir="${build.dir}/obj"> ... <libset libs="shared"> <libpath location="${CORBACPP_HOME}/lib"/> <fileset dir="${CORBACPP_HOME}/lib" includes="libmico.so"/> <fileset dir="${CORBACPP_HOME}/lib" includes="mico"/> </libset> ... </cc> I have tried different variants (see above), but the -verbose output of gcc: [echo] TRYING: /opt/local/mico/lib/libmico.so ... [cc] gcc -o TestGet /tmp/obj/TestGet.o does not show the mico library. any idea what i do wrong? > I guess you are probably using: > > <libset libs="whatever1 whatever2"/> Yes, this was my original form. > > This form was supposed to imply both the installed location and the > extension of the library from the parser. I haven't used it and and not > sure the value of implying the extension. > > The current structure also allows you to > > <libset> > <fileset dir="${build.dir}" includes="mylib.lib"/> > <libset> > > Which would be equivalent to just adding the fileset to the containing <cc> > or <linker> element (the fourth way). > > If you are trying to link with a library found in the library path, try > using the first form. If you are linking with a library that you know the > location of, add a corresponding entry in the overall fileset. If that > doesn't work, it may be because the extension of the library is not > recognized as a type that the linker can consume (currently ".o", ".a" and > ".lib" for GccLinker if I remember correctly). Is it possibly my ".so" extension? thanks again Marcel -- Marcel Ruff mailto:ru...@sw... http://www.lake.de/home/lake/swand/ http://www.xmlBlaster.org |