Am 08.12.2003 22:41:40 schrieb(en) Felix Kühling: > > Am 08.12.2003 18:57:14 schrieb(en) Ian Romanick: [snip] > > Felix would be able to answer better, but I believe the reason was so > > that the config utility could load the *_dri.so and get the list of > > options for that driver. > > Precisely. I forgot that myself for a moment. Anyway, it was specified > that way in all the revisions of the design document and noone > complained. ;-) So for the config tool they need to be external symbols > somewhere in the drivers. We could still specify them as parameters to > driParseOptionInfo to get rid of the dependency of common code on > driver-specific stuff. However, the bigger problem is that you need to > link with libexpat if you link with xmlconfig.o. I don't think we want > that in drivers that don't use config (yet), after all the trouble > people had with it.
Ok, Alan just took care of the libexpat problem. :) I'm going to fix the rest soon. > > Regards, > Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything [EMAIL PROTECTED] \___/ \___/ U at the same time. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
