On Tue, 14 Nov 2017 14:49:01 -0200 Gustavo Sverzut Barbieri <barbi...@gmail.com> said:
> On Tue, Nov 14, 2017 at 10:46 AM, Andrew Williams <a...@andywilliams.me> > wrote: > > Hi, > > > > Actually my custom rule will install correctly as th .eo.h file is the only > > declared output and so no other files are installed. In this way you can > > generate all three files in one eolian_gen pass which is much faster. > > this is what I expect, not parsing every file again, building the same > in memory db again, just to generate different output. > > actually I'd expect one day eolian get some caching in mmap-able > format, making each ".eo" processed in the cache, would speed up a lot > the efl build. I actually suspect that that caching (at least a transparent automatic cache) won't help much because to validate the cache you have to at least stat every single eo file that would normally be parsed first and then compare to cache timestamp. that's going to consume a lot of the overhead alone. If we could avoid this, it'd be better. Perhaps it'd be better to actually have a "system cache". Whenever you install .eo files, after the install of all of them is done, as root run "eolian_cache_update" and it will update maybe /var/cache/eloian-cache.eet or something. Then this is done manually after an install or as a post-install make rule etc. and at least it can cover "system eo files". -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ 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
