Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-16 Thread Jose Fonseca

* --enable-debug  => build=debug (there's also, "profile", "checked", and 
"release")

* --with-xxx --disable-xxx  => just say list target you want, and scons will 
build that target, and all depencies, and nothing more. For example

   scons dri-r600g

It would be nice to have a list of all targets, but I don't know.  Another 
approach is to specify the directory:

   scons src/gallium/targets/dri-swrast/

The rest, --prefix=/usr --enable-glx-tls --enable-texture-float, has no 
equivalent yet: there's no install support, and libGL is not being built yet 
either. Hopefully soon.

Jose



- Original Message -
> OK, I take the scons patches back. I thought scons was only good for
> building llvmpipe and svga on Windows.
> 
> scons --help is not very helpful, it doesn't describe how to build
> drivers. Is there a way to exactly reproduce the following configure
> options in scons?
> 
> --prefix=/usr --enable-glx-tls --enable-debug --enable-texture-float
> --disable-glu --disable-glut --disable-glw
> --with-gallium-drivers=r300,r600,swrast --with-dri-drivers=swrast
> 
> Marek
> 
> On Tue, Jun 14, 2011 at 6:45 PM, Jose Fonseca 
> wrote:
> >
> >
> > - Original Message -
> >> On Tue, 2011-06-14 at 18:25 +0200, Marek Olšák wrote:
> >> > Hi,
> >> >
> >> > This series reworks some of our configure options to make
> >> > Gallium
> >> > easier to configure.
> >> >
> >> > First, there is a new option --with-gallium-drivers=DIRS, which
> >> > replaces the current heap of options --enable-gallium-DRIVER.
> >> > --disable-gallium is removed as well, instead,
> >> > --with-gallium-drivers= without parameters should be used to
> >> > disable Gallium.
> >> >
> >> > --enable-gallium-egl is removed. having --enable-egl and
> >> > --with-gallium-drivers=somedriver is sufficient.
> >> >
> >> > --with-state-trackers is removed as well. The list of state
> >> > trackers is automatically deduced from the --enable-API options
> >> > (the vega,egl state trackers) and --with-driver=dri|xlib (the
> >> > dri,glx state trackers). Some state trackers lack an enable flag
> >> > now, so these two have been added to make the list complete:
> >> > --enable-xorg and --enable-d3d1x.
> >> >
> >> > In order to be able to "git bisect run" through this change, you
> >> > can specify both the old and new options at the same time. Those
> >> > that are unsupported are ignored.
> >> >
> >> > Other than that, I am enabling r600g by default and removing
> >> > r300g
> >> > and r600g from scons. I am not a fan of having multiple build
> >> > systems and most people prefer autoconf anyway. It's not like
> >> > anybody needs to build those drivers on Windows.
> >>
> >> I did use r600g + scons for the little bit of work I did there,
> >> and
> >> if I
> >> went back to it, it would continue to be with scons...
> >>
> >> Is there a significant cost to you having it there?
> >>
> >> Keith
> >
> > Ditto. I've been building r600g on linux with scons too -- scons
> > it's much better for continuous integration/testing, given one
> > doesn't need to do make clean everytime, just to ensure the
> > dependencies are computed correctly.
> >
> > Given that autoconf will never support MSVC, if people don't like
> > multiple build systems, then autoconf+gmake is definely not the
> > one to bet on.
> >
> > I've been (slowly) trying to get scons to build everything, and
> > plan to do so. So that scons can be a viable alternative
> > eventually.
> >
> > Jose
> >
> 
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-15 Thread Marek Olšák
OK, I take the scons patches back. I thought scons was only good for
building llvmpipe and svga on Windows.

scons --help is not very helpful, it doesn't describe how to build
drivers. Is there a way to exactly reproduce the following configure
options in scons?

--prefix=/usr --enable-glx-tls --enable-debug --enable-texture-float
--disable-glu --disable-glut --disable-glw
--with-gallium-drivers=r300,r600,swrast --with-dri-drivers=swrast

Marek

On Tue, Jun 14, 2011 at 6:45 PM, Jose Fonseca  wrote:
>
>
> - Original Message -
>> On Tue, 2011-06-14 at 18:25 +0200, Marek Olšák wrote:
>> > Hi,
>> >
>> > This series reworks some of our configure options to make Gallium
>> > easier to configure.
>> >
>> > First, there is a new option --with-gallium-drivers=DIRS, which
>> > replaces the current heap of options --enable-gallium-DRIVER.
>> > --disable-gallium is removed as well, instead,
>> > --with-gallium-drivers= without parameters should be used to
>> > disable Gallium.
>> >
>> > --enable-gallium-egl is removed. having --enable-egl and
>> > --with-gallium-drivers=somedriver is sufficient.
>> >
>> > --with-state-trackers is removed as well. The list of state
>> > trackers is automatically deduced from the --enable-API options
>> > (the vega,egl state trackers) and --with-driver=dri|xlib (the
>> > dri,glx state trackers). Some state trackers lack an enable flag
>> > now, so these two have been added to make the list complete:
>> > --enable-xorg and --enable-d3d1x.
>> >
>> > In order to be able to "git bisect run" through this change, you
>> > can specify both the old and new options at the same time. Those
>> > that are unsupported are ignored.
>> >
>> > Other than that, I am enabling r600g by default and removing r300g
>> > and r600g from scons. I am not a fan of having multiple build
>> > systems and most people prefer autoconf anyway. It's not like
>> > anybody needs to build those drivers on Windows.
>>
>> I did use r600g + scons for the little bit of work I did there, and
>> if I
>> went back to it, it would continue to be with scons...
>>
>> Is there a significant cost to you having it there?
>>
>> Keith
>
> Ditto. I've been building r600g on linux with scons too -- scons it's much 
> better for continuous integration/testing, given one doesn't need to do make 
> clean everytime, just to ensure the dependencies are computed correctly.
>
> Given that autoconf will never support MSVC, if people don't like multiple 
> build systems, then autoconf+gmake is definely not the one to bet on.
>
> I've been (slowly) trying to get scons to build everything, and plan to do 
> so. So that scons can be a viable alternative eventually.
>
> Jose
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-14 Thread Michel Dänzer
On Die, 2011-06-14 at 09:45 -0700, Jose Fonseca wrote: 
> 
> - Original Message -
> > On Tue, 2011-06-14 at 18:25 +0200, Marek Olšák wrote:
> > > Hi,
> > > 
> > > This series reworks some of our configure options to make Gallium
> > > easier to configure.
> > > 
> > > First, there is a new option --with-gallium-drivers=DIRS, which
> > > replaces the current heap of options --enable-gallium-DRIVER.
> > > --disable-gallium is removed as well, instead,
> > > --with-gallium-drivers= without parameters should be used to
> > > disable Gallium.
> > > 
> > > --enable-gallium-egl is removed. having --enable-egl and
> > > --with-gallium-drivers=somedriver is sufficient.
> > > 
> > > --with-state-trackers is removed as well. The list of state
> > > trackers is automatically deduced from the --enable-API options
> > > (the vega,egl state trackers) and --with-driver=dri|xlib (the
> > > dri,glx state trackers). Some state trackers lack an enable flag
> > > now, so these two have been added to make the list complete:
> > > --enable-xorg and --enable-d3d1x.
> > > 
> > > In order to be able to "git bisect run" through this change, you
> > > can specify both the old and new options at the same time. Those
> > > that are unsupported are ignored.
> > > 
> > > Other than that, I am enabling r600g by default and removing r300g
> > > and r600g from scons. I am not a fan of having multiple build
> > > systems and most people prefer autoconf anyway. It's not like
> > > anybody needs to build those drivers on Windows.
> > 
> > I did use r600g + scons for the little bit of work I did there, and
> > if I
> > went back to it, it would continue to be with scons...
> > 
> > Is there a significant cost to you having it there?
> > 
> > Keith
> 
> Ditto. I've been building r600g on linux with scons too -- scons it's
> much better for continuous integration/testing, given one doesn't need
> to do make clean everytime, just to ensure the dependencies are
> computed correctly. 
> 
> Given that autoconf will never support MSVC, if people don't like
> multiple build systems, then autoconf+gmake is definely not the one to
> bet on.
> 
> I've been (slowly) trying to get scons to build everything, and plan
> to do so. So that scons can be a viable alternative eventually.

That would certainly seem like a better solution. As another example,
scons is currently the only useful way to build 32 and 64 bit binaries
from a single tree.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-14 Thread Jose Fonseca


- Original Message -
> On Tue, 2011-06-14 at 18:25 +0200, Marek Olšák wrote:
> > Hi,
> > 
> > This series reworks some of our configure options to make Gallium
> > easier to configure.
> > 
> > First, there is a new option --with-gallium-drivers=DIRS, which
> > replaces the current heap of options --enable-gallium-DRIVER.
> > --disable-gallium is removed as well, instead,
> > --with-gallium-drivers= without parameters should be used to
> > disable Gallium.
> > 
> > --enable-gallium-egl is removed. having --enable-egl and
> > --with-gallium-drivers=somedriver is sufficient.
> > 
> > --with-state-trackers is removed as well. The list of state
> > trackers is automatically deduced from the --enable-API options
> > (the vega,egl state trackers) and --with-driver=dri|xlib (the
> > dri,glx state trackers). Some state trackers lack an enable flag
> > now, so these two have been added to make the list complete:
> > --enable-xorg and --enable-d3d1x.
> > 
> > In order to be able to "git bisect run" through this change, you
> > can specify both the old and new options at the same time. Those
> > that are unsupported are ignored.
> > 
> > Other than that, I am enabling r600g by default and removing r300g
> > and r600g from scons. I am not a fan of having multiple build
> > systems and most people prefer autoconf anyway. It's not like
> > anybody needs to build those drivers on Windows.
> 
> I did use r600g + scons for the little bit of work I did there, and
> if I
> went back to it, it would continue to be with scons...
> 
> Is there a significant cost to you having it there?
> 
> Keith

Ditto. I've been building r600g on linux with scons too -- scons it's much 
better for continuous integration/testing, given one doesn't need to do make 
clean everytime, just to ensure the dependencies are computed correctly. 

Given that autoconf will never support MSVC, if people don't like multiple 
build systems, then autoconf+gmake is definely not the one to bet on.

I've been (slowly) trying to get scons to build everything, and plan to do so. 
So that scons can be a viable alternative eventually.

Jose
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-14 Thread Alex Deucher
On Tue, Jun 14, 2011 at 12:25 PM, Marek Olšák  wrote:
> Hi,
>
> This series reworks some of our configure options to make Gallium easier to 
> configure.
>
> First, there is a new option --with-gallium-drivers=DIRS, which replaces the 
> current heap of options --enable-gallium-DRIVER. --disable-gallium is removed 
> as well, instead, --with-gallium-drivers= without parameters should be used 
> to disable Gallium.
>
> --enable-gallium-egl is removed. having --enable-egl and 
> --with-gallium-drivers=somedriver is sufficient.
>
> --with-state-trackers is removed as well. The list of state trackers is 
> automatically deduced from the --enable-API options (the vega,egl state 
> trackers) and --with-driver=dri|xlib (the dri,glx state trackers). Some state 
> trackers lack an enable flag now, so these two have been added to make the 
> list complete: --enable-xorg and --enable-d3d1x.
>
> In order to be able to "git bisect run" through this change, you can specify 
> both the old and new options at the same time. Those that are unsupported are 
> ignored.
>
> Other than that, I am enabling r600g by default and removing r300g and r600g 
> from scons. I am not a fan of having multiple build systems and most people 
> prefer autoconf anyway. It's not like anybody needs to build those drivers on 
> Windows.
>
> Please review.

Patches look good to me.

Reviewed-by: Alex Deucher 

>
> BTW, one issue remains:
> In order to build a Gallium EGL driver, st/dri or st/xorg must be enabled (so 
> that the driver's winsys dir is included), even though EGL and its APIs are 
> an entirely separate project. configure.ac has no control over it. The EGL 
> drivers are hardcoded in src/gallium/targets/egl and are compiled if their 
> winsyses are compiled as well.
>
> Marek Olšák (6):
>      configure.ac: remove redundant option --enable-gallium-egl
>      configure.ac: remove --with-state-trackers
>      configure.ac: add option --with-gallium-drivers=DIRS
>      configure.ac: build r600g by default
>      scons: remove r300g from the build system
>      scons: remove r600g from the build system
>
>  Makefile                                      |    1 -
>  configure.ac                                  |  394 
> -
>  src/gallium/SConscript                        |   14 +-
>  src/gallium/drivers/r300/SConscript           |   44 ---
>  src/gallium/drivers/r600/SConscript           |   37 ---
>  src/gallium/targets/dri-r300/SConscript       |   26 --
>  src/gallium/targets/dri-r600/SConscript       |   25 --
>  src/gallium/targets/egl-static/SConscript     |    9 -
>  src/gallium/winsys/SConscript                 |    8 -
>  src/gallium/winsys/r600/drm/SConscript        |   29 --
>  src/gallium/winsys/radeon/drm/SConscript      |   22 --
>  src/mesa/drivers/dri/r300/compiler/SConscript |   51 
>  12 files changed, 128 insertions(+), 532 deletions(-)
>  delete mode 100644 src/gallium/drivers/r300/SConscript
>  delete mode 100644 src/gallium/drivers/r600/SConscript
>  delete mode 100644 src/gallium/targets/dri-r300/SConscript
>  delete mode 100644 src/gallium/targets/dri-r600/SConscript
>  delete mode 100644 src/gallium/winsys/r600/drm/SConscript
>  delete mode 100644 src/gallium/winsys/radeon/drm/SConscript
>  delete mode 100755 src/mesa/drivers/dri/r300/compiler/SConscript
>
> Best regards
> Marek
> ___
> mesa-dev mailing list
> mesa-dev@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/mesa-dev
>
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev


Re: [Mesa-dev] [PATCH 0/6] Overhaul of Gallium configure options

2011-06-14 Thread Keith Whitwell
On Tue, 2011-06-14 at 18:25 +0200, Marek Olšák wrote:
> Hi,
> 
> This series reworks some of our configure options to make Gallium easier to 
> configure.
> 
> First, there is a new option --with-gallium-drivers=DIRS, which replaces the 
> current heap of options --enable-gallium-DRIVER. --disable-gallium is removed 
> as well, instead, --with-gallium-drivers= without parameters should be used 
> to disable Gallium.
> 
> --enable-gallium-egl is removed. having --enable-egl and 
> --with-gallium-drivers=somedriver is sufficient.
> 
> --with-state-trackers is removed as well. The list of state trackers is 
> automatically deduced from the --enable-API options (the vega,egl state 
> trackers) and --with-driver=dri|xlib (the dri,glx state trackers). Some state 
> trackers lack an enable flag now, so these two have been added to make the 
> list complete: --enable-xorg and --enable-d3d1x.
> 
> In order to be able to "git bisect run" through this change, you can specify 
> both the old and new options at the same time. Those that are unsupported are 
> ignored.
> 
> Other than that, I am enabling r600g by default and removing r300g and r600g 
> from scons. I am not a fan of having multiple build systems and most people 
> prefer autoconf anyway. It's not like anybody needs to build those drivers on 
> Windows.

I did use r600g + scons for the little bit of work I did there, and if I
went back to it, it would continue to be with scons...

Is there a significant cost to you having it there? 

Keith

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev