Re: [CEDET-devel] EDE projects for JVM-related languages & build tools
Brought to you by:
zappo
From: Alex O. <al...@gm...> - 2012-10-19 11:02:14
|
Hi I think, that you can start by looking to ede-cpp-root-project and other simple ede-project types. I'm using ede-cpp-root-project for similar tasks (https://github.com/alexott/emacs-configs/blob/master/rc/emacs-rc-cedet.el#L186) - I only specify project's root, compilation command & other options, and retrieve this information when I need to invoke compiler, setup some variables in hook, etc. You can look to my config starting with this line: https://github.com/alexott/emacs-configs/blob/master/rc/emacs-rc-cedet.el#L109 - it automatically fetches compilation command from EDE, and executes it On Fri, Oct 19, 2012 at 11:42 AM, Left Right <ole...@gm...> wrote: > Hello Alex, > > I'm working on HaXe, here's the language homepage http://haxe.org/ if > you are interested. > > The language's compiler can use a special kind of files to build > projects, these are basically a set of compiler options (+ compiler > can forward calls to shell / perform multiple compiles in succession). > For a large range of projects this is sufficient. > What is different from C/C++ compilers is that there is no need to > specify each file that has to be compiled and linked into the program. > The compiler will analyse the dependencies on its own and will find > (or fail to and error) the required dependent sources. > The primary use of the language is the web projects, and a typical > output is not a single binary, it is more of a what would you put into > a WAR file if you were to deploy a Java application into a Java web > server. I.e. a project would most commonly consist of a sources to > compile a web applet, HTML pages (perhaps generated), maybe some > JavaScript code, maybe resources such as images or sound clips etc. > > What I was hoping to store persistently per project is a bunch of > customizations such as: compile-command, compiler's location, standard > library location, contributors library location etc (it is possible to > have multiple copies on your PC and it is a common practice to have > more then one). And a few variables defined by the user (such as > author, version) or formatting settings (such as number of spaces in a > tab, number of tabs to indent, maybe even color theme). From the > coding point of view, All I have to know is the project's root > directory, the list of root source directories and the name of the > file which is the program's entry point. All of these I could infer > from the build script, but this doesn't scale well, because, > obviously, I can't add stuff like source formatting in there. > > What I did like in EDE is the interface :) I.e. I like very much the > customization buffer. It looks like a lot of work to me. I'm not sure > EDE is the right tool for what I want, I just liked how it works for > other things :) > > Best. > > Oleg -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |