while I'm okay with .eo.x, I'm not sure you should include it in "sources", rather do in "dependencies".
as for generating .eo.c and .eo.h independently (mentioned in another email in this thread), don't go that route plz... slows down the process quite a lot :-/ On Tue, Nov 14, 2017 at 6:15 AM, <marcel-hollerb...@t-online.de> wrote: > Hello, > > i am currently looking how we can work with meson in the efl tree. And > quite a big problem came up. Right now we translate a .eo file into a > .eo.c and .eo.h file, where the .eo.c is not a standalone c file, it > must be included, it does not compile by itself. > > In meson we can just put the .eo.c file into the other sources and put > them into library(...) or executable(...) which leads to meson thinking > it needs to compile the file with a c compiler, since the file has the > .c extension. > > My plan is now to generate .eo.x and .eo.h files to solve this > issue, we use .x in our codebase for files that are not usefull in > standalone and must be included in some way. > > Opinions? > > Greetings, > Marcel Hollerbach > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Gustavo Sverzut Barbieri -------------------------------------- Mobile: +55 (16) 99354-9890 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
