On Tue, Nov 14, 2017 at 9:35 AM, <marcel-hollerb...@t-online.de> wrote: > On Tue, Nov 14, 2017 at 09:22:01AM -0200, Gustavo Sverzut Barbieri wrote: >> while I'm okay with .eo.x, I'm not sure you should include it in >> "sources", rather do in "dependencies". > > Well is it a dependency?
that's exactly what it is: a dependency. it's not the source file, which is the .c that devs edit :-) Rather the ".eo" is a source, but the complier doesn't understand it, so we translate so it can be used by c compiler... in an ideal world we could provide "efl_cpp" that wraps cpp and would generate C for you transparently. >> 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 :-/ > > Even if i dont like the argument, right now its the same ... :) huh? when one .eo changes, every other file changes the same way. There is no point to process it 3 times, it's even race-prone... -- 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
