Find a file
Kenneth Graunke 909e889967 glsl: Split up function matching and call generation a bit more.
We used to have one big function, match_signature_by_name, which found
a matching signature, performed out-parameter conversions, and generated
the ir_call.  As the code for matching against built-in functions became
more complicated, I split it internally, creating generate_call().

However, I left the same awkward interface.  This patch splits it into
three functions:
1. match_signature_by_name()

   This now takes a name, a list of parameters, the symbol table, and
   returns an ir_function_signature.  Simple and one purpose: matching.

2. no_matching_function_error()

   Generate the "no matching function" error and list of prototypes.
   This was complex enough that I felt it deserved its own function.

3. generate_call()

   Do the out-parameter conversion and generate the ir_call.  This
   could probably use more splitting.

The caller now has a more natural workflow: find a matching signature,
then either generate an error or a call.

Signed-off-by: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Eric Anholt <eric@anholt.net>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
2012-04-02 14:15:29 -07:00
bin Remove autoreconf generated files 2012-01-30 21:10:10 -05:00
configs darwin: Link against libxcb 2012-03-16 17:09:22 -07:00
docs docs/GL3.txt: document ARB_blend_func_extended state 2012-03-24 16:35:46 +00:00
doxygen doxygen: Add link to the gbm documentation to the header 2012-01-13 09:31:24 -05:00
include intel: add PCI IDs for Ivy Bridge GT2 server variant 2012-04-01 10:50:55 -03:00
scons scons: Update windows llvm libraries for version 3.0. 2012-02-23 12:29:29 +00:00
src glsl: Split up function matching and call generation a bit more. 2012-04-02 14:15:29 -07:00
tests Add Makefile.in to toplevel .gitignore 2012-03-20 11:50:50 -07:00
.emacs-dirvars Add emacs dirvars file with Mesa indention definition. 2007-09-18 10:02:51 -04:00
.gitattributes Allow CRLF automatic conversion on MSVC project files. 2008-06-24 22:25:52 +09:00
.gitignore Add Makefile.in to toplevel .gitignore 2012-03-20 11:50:50 -07:00
acinclude.m4 autoconf: Attempt to figure out the PIC flags for the platform 2008-05-09 07:05:16 -07:00
Android.common.mk android: pass -std=c99 by default 2011-11-26 11:42:08 +08:00
Android.mk android: move libGLES_mesa build rules to src/egl/main/. 2011-11-26 11:42:08 +08:00
autogen.sh autogen.sh: Honor NOCONFIGURE environment variable 2011-09-19 19:53:49 +01:00
common.py scons: Add more machine architectures to the machine map 2012-01-18 16:46:16 +00:00
configure.ac configure: Add --with-llvm-shared-libs 2012-03-30 09:13:04 -04:00
Makefile makefile: add phony am--refresh target 2012-03-25 17:09:35 +01: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.