In continuing to work on KDE, we've run into a couple of interesting problems with the -shlibs splitoff. KDE uses libltdl heavily for dlopening libraries on the fly, and uses the .la's to determine the names of those libraries.
Things will not even start without the .la's, so this will be an issue with the -shlibs packages. There is also the other problem that these modules are unversioned, so they would conflict if going into the -shlibs package. How should this be handled? Only the versioned dylib's go into the -shlibs package, and then all other libs and the .la's go into the main package? It's currently split up by: kdelibs: bin/ and share/ kdelibs-shlibs lib/ (anything dynamic) kdelibs-dev include/ lib/*.la lib/*.a ...but essentially they all have to be installed right now for it to work. I'm assuming that it's going to have to be like so: kdelibs: bin/ share/ lib/ (*.la, and any unversioned library) kdelibs-shlibs: lib/ (any versioned library) kdelibs-dev: include/ lib/ (*.a) Does this make sense? Is this pretty much what we're going to have to do? _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
