On Sun, Mar 25, 2012 at 03:37, Suresh Kumar <[email protected]> wrote: > Hello All, > > Year back I came to know about Enlightenment project while looking for > something in the web, I got inspired by the flexibility and like to > continuously use E17 as my primary window manager. So far so good and I use > Easy_17.sh scripts to build the code and install. now a days it is really > hard if some folders moved / something goes wrong. Besides I didn't see any > update happening to that script. I do modify the scripts to make it build > the e17 code but most of the people interested in final output then going > spending their time on making changes and make it build. > > Recently I have notices that *Language* module moved to Broken and easy_17 > script loops there for hours and I made a change to skip it and now again > stop at *exquisite/m4 *here and searching for this file. I can make that > change but if this is keep happening it would be better to provide build > script with source code and how we know that Language module is back and > working. > > My request would be that E17 team should really focus on build and > configuration as one system for final users at least anyone can download > and install without trouble. It does not mean that I am not saying to > remove current flexibility where user can build each module standalone but > it would be great if we can build as one system just like easy_17.sh but > more stable and updating with every changes of e17 source code if possible > nightly build should use it so that update conforms that build scripts is > update to date. > > Note : Normally I run with FULL option to get all the functionalities. > > I came across CMAKE project and lot of open source tools moving towards to > this build system. But its up to Enlightenment team to come up with best > system for both ( Current and future ) > > -- > -Regards, > Suresh > ------------------------------------------------------------------------------ > This SF email is sponsosred by: > Try Windows Azure free for 90 days Click Here > http://p.sf.net/sfu/sfd2d-msazure > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users
Hello Suresh, you really got a few things mixed up here. Easy_e17.sh is by no means a build system, and certainly not Enlightenments build system. Most of enlightenments sub-projects (libraries, applications, modules, ...) use autofoo (automake, autoconf, and consorts) as a build system. The build system is per application, not for the whole SVN. That's not the buildsystems job and so it will never be done. Easy_e17 however is used to build and install all supported applications in E's SVN by using their build systems. Therefore it is more similar to a simple package manager than a build system. It generally works well and is actively being developed, so if you report bugs they likely will get fixed. As E SVN does change often and quickly, it is necessary to change Easy_e17 now and then, too. Endusers should not use SVN if they expect things to "just work" and so they should not use Easy_e17 unless they're willing to at least report bugs. It is the distributions job to provide the packages for those users. There is no excuse for any distribution not to include the Enlightenment Libraries (EFL), as they experience regular releases. E17 itself has not yet been released, but released snapshots could be easily used for packaging by distributors. The Makefile.linux in E's root directory only builds a small set of packages and thus is not comparable to Easy_e17. ~thomasg ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
