#include <hallo.h> Jack Howarth wrote on Tue Dec 25, 2001 um 11:43:18AM: > After a number of rants from Branden I rather confused now > as to why xlibs-pic exists at all. As best as I can tell through
That is easy. You are not allowed to link static code into shared libraries on certain plattforms. So Branden did develop a working solution: - Applications link with statical xlibs code (*) - other shared libs (SDL-extensions, Allegro, Plugins) intended to use code from static xlibs can link code from the xlibs-pic package. This code is similar to the one used in static libs, but compiled dynamicaly (PIC) (*) This linking is guaranteed by the modified libsdl*debian packages. sdl-config from this packages tells to link with -lXxf86dga -lXxf86vm -lXv > the froth, Branden is saying that absolutely no static libs > should be linked into a shared lib. The conventional wisdom Correct. Distribution ignoring this issue cannot use SDL and some other libs on many architectures. > All libraries must have a shared version in the lib* package and a static > version in the lib*-dev package. The shared version must be compiled with > -fPIC, and the static version must not be. In other words, each *.c file > will need to be compiled twice. Don't wake up sleeping wulfes. One could say, this statements affects only shared library packages, so forget it in this case. > So what is really correct? It would seem that xlibs-pic seems to only Correct is the thing, which works. With libsdl*debian and xlibs-pic we have working solutions to satisfy all we need. Do you have a better solution? No, no, no, you can only dream about one. If you want to change things extremely, convince the Xfree86 project to use proper SONAMES and stable ABI for their libs. Currently, this is not possible. > encourage breaking the current new stricter policy on shared libs not > containing static libs. I am very unclear as to what is the approved Policy should serve the social contract and be modified as needed. > fix then. If something like libsdl-image should not link any static lib > (even built with -fPIC) into its shared libs, then what use is xlibs-pic Hello? -pic is intended to provide the shared code where static X libs were used previously. > at all? If we are going to enforce this darconian rule then xlibs-pic > should be depreciated out of xfree86 since it can't actually be used > without violating current debian policy. Nice Catch22. My prophet, we are really glade to hear your non-constructive, needless and useless critism. Go away and use RedHat where you allways get working solutions, for more plattforms, better code, hotdogs falling from the sky, etc. etc. Gruss/Regards, Eduard.
