Summary: | Windows binaries | ||
---|---|---|---|
Product: | piglit | Reporter: | anatoly techtonik <techtonik> |
Component: | tests | Assignee: | Piglit Mailing List <piglit> |
Status: | RESOLVED MOVED | QA Contact: | Piglit Mailing List <piglit> |
Severity: | enhancement | ||
Priority: | medium | CC: | jfonseca |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
anatoly techtonik
2016-02-08 13:05:38 UTC
I build piglit on Windows continously. It's in fact trivial to build Windows piglit binaries on Linux with MinGW cross compilers. But even if I find a way to upload piglit windows binaries somewhere to freedesktop.org, it's not trivial to run: end users would also need to install Python, and a bunch of Python modules. One could try to bundle Python Windows binaries and modules too, but that's a lot of work. I think the best is to take the indidual test .exe and .dll and data files, and explain how to invoke the test directly (without the Python framework.) But all things considered, I'm afraid making it easier for non-technical Windows end users to run Piglit seems a huge time sink, and give no return. I think that projects like godotengine can and should accomplish this on their own: - build piglit for Windows (e.g., using Mingw) - for every bug the engine runs against, zip individual tests executables and dll, and post somewhere else -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/piglit/issues/3. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.