On Thu, Mar 23, 2017 at 4:56 PM, Dylan Baker <dylan@xxxxxxxxxxxxx> wrote: > Quoting Colin Cross (2017-03-23 15:14:16) >> On Thu, Mar 23, 2017 at 2:56 PM, Greg Hackmann <ghackmann@xxxxxxxxxx> wrote: >> > On 03/22/2017 02:48 PM, Rob Clark wrote: >> >> >> >> On Wed, Mar 22, 2017 at 4:10 PM, Dylan Baker <dylan@xxxxxxxxxxxxx> wrote: >> >>> >> >>> Quoting Rob Clark (2017-03-22 10:07:54) >> >>>> >> >>>> I guess an interesting question (from someone who doesn't know meson >> >>>> yet) would be whether meson could slurp in the Makefile.sources type >> >>>> stuff that we have, which are shared so far between >> >>>> android/scons/autotools (and for the most part, kept developers from >> >>>> having to care *too* much about the different build systems) >> >>> >> >>> >> >>> Jason and I have talked about that too. I'd suggested that we could write >> >>> a >> >>> module for meson to read makefile.sources (since we're surely not the >> >>> only >> >>> project that would benefit from such a module), except that android is >> >>> moving to >> >>> blueprint[1] instead of android.mk files. As far as I can tell blueprint >> >>> doesn't >> >>> support using makefile.sources, so it seems somewhat moot in a world of >> >>> blueprint for android, meson for *. >> >> >> >> >> >> I guess even if it is only a temporary thing, something that could >> >> slurp in Makefile.sources seems like it would be useful for a >> >> transition period. >> >> >> >> I'm not totally up to speed on android/blueprint stuff.. but even some >> >> simplified or different "here-are-my-sources" type file that could be >> >> shared across build systems would be useful. Meson sounds a bit more >> >> extensible so maybe there is some potential to adapt to whatever >> >> android forces on us ;-) >> > >> > >> > +ccross from the Android build team can hopefully provide some input here. >> >> For cases like this, we generally add a python script that translates >> the build files into something Blueprint understands, and rerun it >> each time we import into the project. >> >> Alternatively, Blueprint efficiently supports globbing for sources, so >> if all the source files are always listed in Makefile.sources (which >> seems to be true in our copy of libdrm except for intel/test_decode.c) >> then we could use globs and ignore the makefiles, possibly manually >> excluding a few files. > > I'm hoping you can clarify a couple of questions I have about blueprint: > 1) android is moving to blueprint from android.mk files? Yes, in a phased transition. We support both for now. > 2) is there a publicly available project that uses blueprint I could look at? > The documentation I've been able to find is pretty sparse. Blueprint is a framework for writing build systems, and Soong is AOSP's Blueprint build system. See https://android.googlesource.com/platform/build/soong/+/master/README.md for documentation on Soong. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
