Find a file
Paul Berry 42a29d89fd glsl: Eliminate ambiguity between function ins/outs and shader ins/outs
This patch replaces the three ir_variable_mode enums:

- ir_var_in
- ir_var_out
- ir_var_inout

with the following five:

- ir_var_shader_in
- ir_var_shader_out
- ir_var_function_in
- ir_var_function_out
- ir_var_function_inout

This eliminates a frustrating ambiguity: it used to be impossible to
tell whether an ir_var_{in,out} variable was a shader in/out or a
function in/out without seeing where the variable was declared in the
IR.  This complicated some optimization and lowering passes, and would
have become a problem for implementing varying structs.

In the lisp-style serialization of GLSL IR to strings performed by
ir_print_visitor.cpp and ir_reader.cpp, I've retained the names "in",
"out", and "inout" for function parameters, to avoid introducing code
churn to the src/glsl/builtins/ir/ directory.

Note: a couple of comments in the code seemed to indicate that we were
planning for a possible future in which geometry shaders could have
shader-scope inout variables.  Our GLSL grammar rejects shader-scope
inout variables, and I've been unable to find any evidence in the GLSL
standards documents (or extensions) that this will ever be allowed, so
I've eliminated these comments.

Reviewed-by: Carl Worth <cworth@cworth.org>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Eric Anholt <eric@anholt.net>
2013-01-24 16:30:30 -08:00
bin Remove installmesa 2013-01-10 22:01:31 +01:00
docs GL3.txt: i965 supports ARB_base_instance 2013-01-22 21:34:25 -08:00
doxygen glsl/build: Build glcpp via the glsl Makefile 2013-01-22 14:33:20 -08:00
include dri: Define enum __DRI_API_GLES3 2013-01-15 13:45:53 -08:00
m4 build: Use AX_PROG_FLEX 2013-01-22 14:33:38 -08:00
scons scons: Fix source lists parsing on Windows. 2013-01-23 12:11:53 +00:00
src glsl: Eliminate ambiguity between function ins/outs and shader ins/outs 2013-01-24 16:30:30 -08:00
.dir-locals.el Add emacs setup for the docs/devinfo.html comment wrapping recommendation. 2012-07-11 09:20:21 -07:00
.gitattributes Disable autocrlf for Visual Studio project files. 2008-02-28 12:34:01 +09:00
.gitignore Clean up .gitignore files 2013-01-10 22:01:31 +01:00
Android.common.mk android: Define Make variables for Android version 2013-01-02 14:51:18 -08:00
Android.mk android: Define Make variables for Android version 2013-01-02 14:51:18 -08:00
autogen.sh build: Fix autogen.sh to allow out-of-tree builds 2012-08-14 10:54:39 -07:00
common.py scons: Add option to enable floating-point textures. 2012-08-15 22:04:24 -07:00
configure.ac configure.ac: Force use of LLVM shared libs with --enable-opencl v2 2013-01-24 15:45:18 +00:00
Makefile.am glsl/build: Build tests via the glsl Makefile 2013-01-22 14:33:24 -08:00
SConstruct scons: Disable saving options automatically. 2011-07-01 19:04:57 +01:00

File: docs/README.WIN32

Last updated: 23 April 2011


Quick Start
----- -----

Windows drivers are build with SCons.  Makefiles or Visual Studio projects are
no longer shipped or supported.

Run

  scons osmesa mesagdi

to build classic mesa Windows GDI drivers; or

  scons libgl-gdi

to build gallium based GDI driver.

This will work both with MSVS or Mingw.


Windows Drivers
------- -------

At this time, only the gallium GDI driver is known to work.

Source code also exists in the tree for other drivers in
src/mesa/drivers/windows, but the status of this code is unknown.


General
-------

After building, you can copy the above DLL files to a place in your
PATH such as $SystemRoot/SYSTEM32.  If you don't like putting things
in a system directory, place them in the same directory as the
executable(s).  Be careful about accidentially overwriting files of
the same name in the SYSTEM32 directory.

The DLL files are built so that the external entry points use the
stdcall calling convention.

Static LIB files are not built.  The LIB files that are built with are
the linker import files associated with the DLL files.

The si-glu sources are used to build the GLU libs.  This was done
mainly to get the better tessellator code.

If you have a Windows-related build problem or question, please post
to the mesa-dev or mesa-users list.