Thomas Pegg wrote:


I can give you the link myself: http://www.tpegg.org/20051203/

Just a fair warning this a preliminary setup, there's still some more pieces that need to be added.

I should add some more to this, hit send too quick.

As you can tell this would add about 200+ (if my count is right) packages to the book. Quite a beast.

First, this current render is for RC3 (and is based off of BLFS SVN 20051203), and is missing sections for the data, doc and util modules. I'm doing some work to get it to the 7.0 release, plus adding those sections.

Next, two new packages will most likely need to be added to the book as they are requirements for the server package, Mesa (this is needed to have the GL libraries plus you need to have the unpacked Mesa source lying around to compile DRI support into the server) and libdrm.

Most things in the various modules of the build can be build in any order, with the exception of the Library section which is setup in dependency order. But the modules themselves have to built in a specific order, Proto -> Libs -> Apps -> Server -> Driver -> Data -> Font -> Util.

I followed the script here ( http://cvs.freedesktop.org/xorg/util/modular/build.sh?rev=1.63&view=log) and the Modular Developer's Guide on the X.org site to set most of this up.

One thing they do in the script is they put the Doc module ahead of proto, I haven't done that in my builds, I haven't seen any adverse affects from not doing it (it doesn't do much other than installing an entity file).

I've maintained installing everything into the /usr/X11R6 heirarchy, this should probably be X11R7, but I'm not sure. Could easily use a symlink for compaitibilty sake.

And there's still a lot of detail work to be done, things like what each package is for, the contents (some of this I haven't done on purpose, because I wasn't sure what should be included, the editor's guide doesn't give any guidance on it).

Thomas

--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to