Michael Jennings wrote: > On Tuesday, 22 May 2007, at 14:01:16 (-0400), > Christopher Michael wrote: > >>> yes. modules should exclude *.a files. libtool insists on creating them and >>> installing them because it thinks its needed as we will then use them >>> (libtldl >>> in theory can in combination with module.la). note that the sample package >>> files for e17 remove any .a's for modules >>> same for evas and emotion. >> I do have to (respectfully) disagree with you on this one. I just >> checked the "official" E modules installations, and they are also >> installing module.a files in /usr/lib/enlightenment/modules/<module>. > > No, raster's right. Using libtool basically forces us to install the > *.a files with "make install," but if you look at the spec files for > e, evas, etc., you'll see this: > > rm -f `find $RPM_BUILD_ROOT/usr/lib/enlightenment -name "*.a" -print` > > I think you were confused about what "sample package files" meant. > > Michael > My confusion is Very Possible Michael :) I know barely nothing of "packaging"...was just simply stating that they do get installed via "make install" from a "normal" cvs build :) No disrespect intended to anyone.
dh ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
