On Sat, 24 Mar 2012 21:37:31 -0400 Suresh Kumar <uniquesur...@gmail.com> said:
i do think you are a bit confused here. easy-e17 is a script that walks many sub-projects (libs an apps) and builds those. each and every project has a build "system" (autoconf/automake and friends) already. easy-e17 takes over the job a developer (or packager) would normally do for you and does a very fine job of it considering it has to deal with a LIVE codebase thats is fluid and keeps changing. as such cmake IS a replacement for autoconf/automake etc. so that's a "red herring" - it doesn't help in your case, it just changes what we have. (the debate on cmake vs autofoo is a topic all of its own and i won't go into that here). if you want easy - use packages made for your distro. there are many options. if your distro doesn't have packages, then it's not popular enough to be supported, so you either support yourself, or change distro. your 2 problems are inherent problems of dealing WITH a live source tree. we developers deal with them every day. the m4 problem is due to there being auto-generated files or directories in your local tree that NOW have become managed by svn. EVERY SCMS will complain in this situation as it has a conflict. your solution would be to WIPE your entire svn checkout tree every time before running easy_e17.sh. (i can come up with other imaginative solutions, but they all will either consume extra disk space). by using easy_e17.sh you are taking on the role of a packager or developer, but its SO easy, you barely notice, and when something does go wrong, you will need to deal with it just like packagers/developers. providing feedback on error cases easy_e17 doesn't handle well is useful and morlenxus can improve it - or send patches to the script to improve it. the language module moving issue is again normal - we move things around. as such a big issue is that easy_e17 supports building LOTS of things in SVN that are not actively maintained or released. things crawling with bugs that will never have them fixed. look at our download page and see what set of projects actually make it to release. those also will make it to packages too - or should. one thing you want to be wary of *IS* building everything. building just core things we release is safe, unless you want to start dealing with breakages often. supporting releases in a linux world inherently is nasty and hard, due to the 1000+ linux distros and packaging. thus MOST projects just release source tarballs and leave it up to each distros packagers to packages stuff. this is just how it works as doing it all ourselves is nigh impossible. even so - we DO have packages built by team and community members for some distros. > 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 > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ 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 enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
