No description
Find a file
Eric Anholt 7029ec05e2 gallium: Add renderonly-based support for pl111+vc4.
This follows the model of imx (display) and etnaviv (render): pl111 is a
display-only device, so when asked to do GL for it, we see if we have a
vc4 renderer, make the vc4 screen, and have vc4 call back to pl111 to do
scanout allocations.

The difference from etnaviv is that we share the same BO between vc4 and
pl111, rather than having a vc4 bo and a pl11 bo and copies between the
two.  The only mismatch between their requirements is that vc4 requires
4-pixel (at 32bpp) stride alignment, while pl111 requires that stride
match width.  The kernel will reject any modesets to an incorrect stride,
so the 3D driver doesn't need to worry about that.

v2: Rebase on Android rework, drop unused include.
v3: Fix another Android bug, from Rob Herring's build-testing.

Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
2017-06-15 11:41:22 -07:00
bin bin/get-fixes-pick-list.sh: better identify multiple "fixes:" tags 2017-06-15 15:53:21 +03:00
docs radeonsi: enable ARB_bindless_texture 2017-06-14 10:04:36 +02:00
doxygen
include i965/cnl: Add a preliminary device for Cannonlake 2017-06-09 16:03:00 -07:00
m4
scons scons: update for LLVM 4.0 2017-05-04 18:05:04 +01:00
scripts
src gallium: Add renderonly-based support for pl111+vc4. 2017-06-15 11:41:22 -07:00
.dir-locals.el dir-locals.el: Adds White Space support 2016-11-14 19:17:49 +02:00
.editorconfig editorconfig: Fix up the tab rendering width. 2017-01-03 10:38:53 -08:00
.gitattributes
.gitignore
.mailmap
.travis.yml gallium: Add renderonly-based support for pl111+vc4. 2017-06-15 11:41:22 -07:00
Android.common.mk util/vulkan: Move Vulkan utilities to src/vulkan/util 2017-06-06 08:17:13 -07:00
Android.mk gallium: Add renderonly-based support for pl111+vc4. 2017-06-15 11:41:22 -07:00
appveyor.yml appveyor: Update dependencies. 2017-03-29 11:53:03 +01:00
autogen.sh
CleanSpec.mk
common.py scons: Recognize LLVM_CONFIG environment variable. 2016-11-24 13:37:33 -08:00
configure.ac gallium: Add renderonly-based support for pl111+vc4. 2017-06-15 11:41:22 -07:00
install-gallium-links.mk
install-lib-links.mk
Makefile.am gallium: Add renderonly-based support for pl111+vc4. 2017-06-15 11:41:22 -07:00
REVIEWERS REVIEWERS: add autogen.sh to the autoconf group 2017-03-23 14:50:51 +00:00
SConstruct
VERSION docs: add 17.2.0-devel release notes template, bump version 2017-04-17 14:31:41 +01:00

File: docs/README.WIN32

Last updated: 21 June 2013


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

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

Run

  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.

Recipe
------

Building on windows requires several open-source packages. These are
steps that work as of this writing.

- install python 2.7
- install scons (latest)
- install mingw, flex, and bison
- install pywin32 from here: http://www.lfd.uci.edu/~gohlke/pythonlibs
  get pywin32-218.4.win-amd64-py2.7.exe
- install git
- download mesa from git
  see https://www.mesa3d.org/repository.html
- run scons

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.