Hi Tim, I have no objections against getting this merged, although here are a couple of things that should be sorted. Some of these are just reiteration from others:
- First and foremost - please base your work against master. Mesa, alike most other open-source projects, tries to keep features out of bugfix releases. As such basing things against 11.0 is not suitable. - Further combinatorial explosion of build configurations - with internal/external core, swr-arch, etc. Some of these can (should?) be nuked, although further comments will follow as patch(es) hit the mailing list. - Using llvm's C++ interface, building against multiple LLVM versions. If openswr only supports only limited versions of llvm, then the build should bail out accordingly - more comments/suggestions as patch(es) hit the ML. - Will patches porting core openswr functionality from the internal tree be part of the public discussions ? The VMWare people have done a great thing trying to keep things open, and people have, on the rare occasion, found nitpicks in their patches. - And last but not least - please split patches sensibly, for your submission and further work). The "Initial public Mesa+SWR" touches files in quite a few different places. Mildly related - I'll be resending/merging a series with reworks things in src/gallium/auxiliary/target-helpers/ so things might clash as you rebase your work. Thanks Emil _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
