summaryrefslogtreecommitdiffstats
path: root/src/gallium/targets/SConscript
Commit message (Collapse)AuthorAgeFilesLines
* gallium: new raw gallium interface to support standalone testsKeith Whitwell2010-03-281-0/+5
| | | | | | | | Provides basic window system integration behind a simple interface, allowing tests to be written without dependency on either the driver or window system. With a lot of work, could turn into something like glut for gallium.
* gallium: Fix DRI driver build warnings under sconsJakob Bornecrantz2010-03-261-64/+2
| | | | | | | When building more then one dri driver we would get warnings because we where defining the same build target multiple times. Also move all the dri scons targets related code into its own file.
* i915g: Rename winsys prefix to i915_ from intel_Jakob Bornecrantz2010-03-261-1/+1
| | | | Since the winsys isn't shared with i965 and never will be
* gallium: Make scons build dri/xorg drivers againJakob Bornecrantz2010-03-241-0/+68
|
* scons: Fixup the libgl-gdi build.José Fonseca2010-03-101-5/+5
|
* scons: Add new targets option.José Fonseca2010-03-091-1/+1
| | | | | This will likely change. Most probably we'll just add an alias to indvidual targets and use the regular scons targets arguments.
* gallium: introduce target directoryKeith Whitwell2010-03-081-0/+16
Currently there are still at least two functions bundled up inside the winsys concept: a) that of a backend resource manager, sometimes capable of performing present() operations, b) the initialization code/routine for the whole driver stack. The inclusion of (b) makes it difficult to share implementations of (a) between different drivers. For instance, a clean xlib winsys could be of use for software-rasterized VG, GLES, EGL, etc, stacks. But that is only true as long as there is no dependency from the winsys to higher level code, as would be the case when we include (b) in this component. This change creates a new gallium/targets subtree, specifically for implementing the glue needed to build individual driver stacks, and moves that code out of a single example winsys, namely xlib. Other drivers continue to build unchanged, but hopefully can migrate to this structure over time.