On 2/14/08, José Fonseca <[EMAIL PROTECTED]> wrote:
> I'll dedicate some time now to reorganize gallium's code & build process. 
> This is
> stuff which has been discussed internally at TG several times, but this time I
> want to get it done.
>
> My objectives are:
>  - leaner and more easy to understand/navigate source tree
>  - reduce (or even eliminate) merges between private branches of the common 
> gallium parts
>  - help keep the gallium tree portable, by keeping things separate.
>
> My plan is:
>
> 1. Physically separate gallium source code from mesa code. This will be the
> final layout:
>
> - src/mesa
> - src/gallium
>   - state_tracker
>     - ogl
>     - ...
>   - drivers
>     - i915simple
>     - i965simple
>     - cell
>     - ...
>   - winsys
>     - dri
>       - intel
>       - ...
>     - xlib
>     - ...
>   - aux
>     - tgsi
>     - draw
>     - pipebuffer
>     - llvm
>     - cso_cache
>     - ...
>
> i.e., give a subdir in src/gallium to each gallium architectural layer.
>
> 2. Eliminate mesa includes out of the gallium source code from
> everything but mesa's state_tracker.

This is finished now.

> 3. Using scons, enhance the build system to support all platforms we are 
> interested (i.e., linux and win32, atm),

I'm working on this now. ATM you can easily do "compile-testing" of
your changes on many gallium variants from a single tree by executing
(e.g., from a script):

   scons dri=0
   scons dri=1
   scons llvm=1

And it can be done regardless of what config is enabled, as it won't
affect the conventional Makefile build. The end result is still not
usable in a few cases (due to library interdependencies issues on
linking, and lack of an "install" target). I'm going to see if I can
get cell and win32 working this way too.

Jose

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to