Hi all, EFL provides compile and runtime checking of version with <NAME>_VERSION_(MAJOR|MINOR), followed by an extern symbol that is defined in runtime.
Problem is maintaining all this crap, now that it is unified we could use a simpler approach to do this and have a single place where it is defined, every other place just reuses that. Example: #include <efl_vesion.h> #define EVAS_VERSION_MAJOR EFL_VERSION_MAJOR #define EVAS_VERSION_MINOR EFL_VERSION_MINOR extern Efl_Version *Evas_Version; I don't think there is much to be discussed about this, what I want to discuss is where to place efl_version.h Should we install it on its own, declaring /usr/include/efl-@VMAJ@ and add it there, alongside with an efl.pc? Or given that every module out there relies on Eina we can do it for Eina and reuse everywhere? -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
