Re: [CEDET-devel] EDE binary file organizaion
Brought to you by:
zappo
From: Eric M. L. <eri...@gm...> - 2012-02-29 03:49:41
|
Hi, The nice thing about Automake for EDE, is that the EDE targets and data can be written directly into Automake files with roughly equivalent behaviors. When EDE generates Makefiles, it has to create variables, rules, and other things to support the relatively simple target, making support a lot more challenging. Recommendations for changes in EDE's support of creating Automake files will be easy as long as EDE just needs to write some configuration into the Automake or Autoconf files. (ie - your suggested options for where to put some of the objects, tools, or config files.) If automake doesn't support it then EDE probably won't be able to either. For SCons, the only support is via a "generic" project type. That basically means it will find the project, tag the root, and can call SCons for you when you choose the EDE compile command. It won't be able to create an SConstruct file. If SConstruct file writing support is desired from the EDE project type that creates Makefiles, then someone who knows how to use it just needs to show that there is a mapping between the EDE and SCons concepts. If that mapping is simple, (ie - a program maps to specific rules in SCons) then adding it would be straight forward, if time consuming. If the mapping is more complex, then complex support (such as the Makefile compiler support in EDE) would need to be developed, and may be too complex to add while keeping maintainability of EDE. I won't claim anything is impossible though. Any such contributor would also need to sign assignment papers w/ the FSF so that said changes could be included in Emacs. Eric On 02/28/2012 09:33 PM, Chris Perivolaropoulos wrote: > The reason ede is a heavenly gift for me! xD > I did a short research and the best I could find was this: > http://www.gnu.org/software/automake/manual/html_node/VPATH-Builds.html#VPATH-Builds > In other words "create the makefile.am and the makefile as you would but > to actually build anything cd to where you want your executable to be > and build from there". Another solution would be to actually move the > executable and the .o files to some predefined directory but that is > dirty, ugly and not useful. Also the libdir and bindir directories seem > to affect only installation. > > Since we are looking into the feature it would be nice to be able to > define a different directory for each target, like with an option in > configure-project. > > Something that is quite important to be taken care of though is I think > the object and other files that clutter the directory tree. I made a 3 > file random project that i expected to have no more than 5-6 files in > total and i ended up with this. > . > |-- aclocal.m4 > |-- AUTHORS > |-- autom4te.cache > | |-- output.0 > | |-- output.1 > | |-- requests > | |-- traces.0 > | `-- traces.1 > |-- ChangeLog > |-- config.guess > |-- config.h > |-- config.h.in > |-- config.log > |-- config.status > |-- config.sub > |-- configure > |-- configure.ac > |-- COPYING > |-- depcomp > |-- include > | |-- cards.h > | |-- debug.h > | |-- Makefile > | |-- Makefile.am > | |-- Makefile.in > | `-- Project.ede > |-- INSTALL > |-- install-sh > |-- libtool > |-- ltmain.sh > |-- Makefile > |-- Makefile.am > |-- Makefile.in > |-- missing > |-- NEWS > |-- Project.ede > |-- README > |-- src > | |-- cards > | |-- cards.c > | |-- cards.lo > | |-- cards.o > | |-- liblibcards.la > | |-- main.c > | |-- main.o > | |-- Makefile > | |-- Makefile.am > | |-- Makefile.in > | `-- Project.ede > |-- stamp-h > `-- stamp-h1 > > I am not really sure how many of these are crucial to be in the root > directory but I would be really dissappointed if it were impossible to > tidy the place up a little. > > On a related note: how long a road is the implementation of scons > project management in ede (I mean ede actually realizing the properties > of the project from the Sconstruct file and the other way around)? > > On 02/29/2012 03:08 AM, Eric M. Ludlam wrote: >> Hi, >> >> If anyone knows how to get automake to do that via calls to configure, >> automake, or whatever, we can add it to EDE. Using various automake >> options by EDE is pretty easy as long as I know what they are. For >> me, figuring out Automake is the real challenge. >> >> Eric > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Cedet-devel mailing list > Ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedet-devel > |