https://bugs.freedesktop.org/show_bug.cgi?id=101614
--- Comment #7 from Trevor SANDY <trevor.sa...@gmail.com> ---
You can see in options listing of the logged output I posted all the component
versions of my MSYS/MINGW dev env.
I'm using...
- MSYS bash at /usr/bin
- MSYS python at /usr/bin (#02 below)
For python, be careful. There are 3 instances available for MSYS/MinGW which
can cause the native windows/posix confusion you describe. They are:
1. Native win32 python: From python.org, sys.platform == "win32", os.path.sep
== "", os.name == "nt"
2. MSYS2 python: "msys2/python2" package installed in /usr/bin/python,
sys.platform == "msys", os.path.sep == "/", os.name == "posix"
3. mingw64 python: "mingw64/mingw-w64-x86_64-python2" package, installed in
/mingw64/bin/python, sys.platform == "win32", os.path.sep == "/", os.name ==
"nt"
If you use MSYS' package manager to setup your MSYS components, scons will be
in base-devel so it will be deposited in /usr/bin so it will rightly use the
python instance located there also - which happens to be the msys/posix
instance. This instance of python will properly interpret your paths as unix
paths.
Native windows and mingw64 python will interpret paths as Windows paths. If you
setup MinGW outside of MSYS like it is described here
https://stackoverflow.com/questions/17871781/building-mesa-for-windows-7-mesa-9-1,
your setup will likely not properly interpret unix paths even if you run it
from a MSYS command shell.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
