Skip to content

Commit

Permalink
Release 18.0.0.600-1
Browse files Browse the repository at this point in the history
Build script documentation: Remove unofficial way of loading git environment
  • Loading branch information
pal1000 committed Mar 28, 2018
1 parent 4ffcf11 commit 7d1f556
Show file tree
Hide file tree
Showing 5 changed files with 11 additions and 11 deletions.
4 changes: 2 additions & 2 deletions buildenvconf.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ OS | Windows 10 Version 1709 Pro x64
| | |
|-|-|
Edition | 2017 Community
Version | 15.6.3
Version | 15.6.4
Windows 10 SDK Version | 10.0.16299.91
Windows 10 SDK install method | standalone
### LLVM
Expand Down Expand Up @@ -53,7 +53,7 @@ Flex version | 2.6.4
### Git version control
| | |
|-|-|
Git For Windows portable | 2.16.2.1
Git For Windows portable | 2.16.3.1
### Mesa3D
| | |
|-|-|
Expand Down
7 changes: 2 additions & 5 deletions buildscript/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,7 @@ Before continuing prepare an empty folder to extract the rest of dependencies in

- [Git for Windows 32 or 64-bit](https://git-scm.com/download/win);

You can use the portable version if you don't want to bloat your system too much, but you have to either launch the build script from within git-cmd.exe session (git-cmd.exe is located in Git installation directory) or add the following locations to PATH:
a. for 64-bit Git: %gitlocation%\bin;%gitlocation%\mingw64\bin;%gitlocation%\cmd
b. for 32-bit Git: %gitlocation%\bin;%gitlocation%\mingw32\bin;%gitlocation%\cmd
Replace %gitlocation% with the actual location where you unpacked Git Portable.
You can use the portable version if you don't want to bloat your system too much, but you have to either launch the build script from within git-cmd.exe session (git-cmd.exe is located in Git installation directory) or run git-cmd.exe with this build script as argument (ex asuming git was instaled in c:\dev\git and this project repository was cloned in c:\dev\mesa-dist-win : "c:\dev\git\git-cmd.exe" "c:\dev\mesa-dist-win\buildscript\build.cmd").
- Mesa source code: [Mirror 1](https://www.mesa3d.org/archive/), [Mirror 2](https://mesa.freedesktop.org/archive/);

The build script can grab Mesa3D code if Git is in PATH. It asks for the branch to pull from. Otherwise manually extract in `.`. Be warned that the archive is double packed. Rename extracted folder to `mesa`.
Expand All @@ -28,7 +25,7 @@ The build script can grab Mesa3D code if Git is in PATH. It asks for the branch
Extract LLVM code in `.`. Rename extracted folder to `llvm`. LLVM 4.0 is the minimum version supported by this build scrpt as Visual Studio 2017 is the only version supported. Required to build high-performance drivers and libraries llvmpipe, swr, osmesa gallium JIT and graw.
- [Ninja build system](https://github.com/ninja-build/ninja/releases)

Optional, it reduces LLVM build size as it works with single configuration. Unlike Visual Studio MsBuild which requires a Release and a Debug configuration at minimum. Development on Ninja stalled shortly after 1.8.2 release for unknown reason though. If used, extract Ninja in `.\ninja`. My script asks if you want to do this before starting LLVM build. LLVM must be built in release mode with install target. This build script does it automatically or you can look [here](https://wiki.qt.io/MesaLlvmpipe).
Optional, it reduces LLVM build size as it works with single configuration. Unlike Visual Studio MsBuild which requires a Release and a Debug configuration at minimum. Development on Ninja stalled shortly after 1.8.2 release for unknown reason though. If used, extract Ninja in `.\ninja`. If ninja is in PATH my script asks if you want to use it when building LLVM. LLVM must be built in release mode with install target. This build script does it automatically or you can look [here](https://wiki.qt.io/MesaLlvmpipe).

- [CMake 32 or 64 bit](https://cmake.org/download/#latest);

Expand Down
2 changes: 1 addition & 1 deletion mesa3d.iss
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
; SEE THE DOCUMENTATION FOR DETAILS ON CREATING INNO SETUP SCRIPT FILES!

#define MyAppName "Mesa3D software rendering drivers for Windows"
#define MyAppVersion "17.3.7.600-1"
#define MyAppVersion "18.0.0.600-1"
#define MyAppPublisher "Pal100x"
#define MyAppURL "https://github.com/pal1000/mesa-dist-win"
#define MyAppExeName "mesa-{#MyAppVersion}-setup.exe"
Expand Down
2 changes: 1 addition & 1 deletion readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
- [Manual OpenGL context configuration](#manual-opengl-context-configuration)

# Downloads
Mesa 17.3.7 builds are now available in [releases section](https://github.com/pal1000/mesa-dist-win/releases)
Mesa 18.0.0 builds are now available in [releases section](https://github.com/pal1000/mesa-dist-win/releases)

# Package contents
The following Mesa3D drivers are shipped in each release:
Expand Down
7 changes: 5 additions & 2 deletions releasenotes.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,12 @@
# Upcoming release
# 18.0.0.600-1
- Updated Mesa3D to [18.0.0](https://www.mesa3d.org/relnotes/18.0.0.html)
### Build environment updates
- pip 9.0.2 -> 9.0.3
- Visual Studio 15.6.3 -> 15.6.4
- git 2.16.2.1 -> 2.16.3.1
### Build guide
- Remove a relic about Windows XP/PosReady 2009, it is no longer supported since Mesa3D 17.2.0;
- Expand section about Git portable with clear details on how you can load Git in PATH.
- Describe the official way of loading git in PATH when using Git portable.
### Deployment
- Add uninstall and update support to system-wide deployment tool.
# 17.3.7.600-1
Expand Down

0 comments on commit 7d1f556

Please sign in to comment.