A parser generator for Emacs

Diez Roggisch | 26 Jun 2012 12:16

ede-simple-project - how to? and some other questions

Hi there,

I'm using the CEDET 1.1 release with emacs 23 under OSX.

I'm interested in managing our existing (huge, own build-infrastructure)
C++-project using EDE.

I want to

 - persist settings as current wordsize for build (32/64 bit), target
(debug/release) and various other settings such as running/debugging in
specific modes
 - setup semantic, possibly using clang, for code-completion and
source-code navigation

I thought that ede-simple-project would be best, because cpp-root-project
isn't suitable (or can it store values such as wordsize or target
dynamically, not in the .emacs?). But when I invoke ede-new, I'm only
offered 

ANDROID ROOT 	ARDUINO SKETCH
Automake 	GNUstep-Make
GNUstep-Make in scanner mode 	GNUstep-make Top Most
Make

No simple. 

Any suggestions?

Thanks,

(Continue reading)

headers

Eric Ludlam | 26 Jun 2012 14:46

Re: ede-simple-project - how to? and some other questions

The ede-simple project type was deprecated. It shouldn't be in any of the distributions anymore either. Perhaps there are other references around we still need to get rid of? The replacement would be the generic project type. The examples are at the end of the ede generic.el file. It will let you persist some changes to build and debug commands..

If your large codebase has others who will be sharing your work you will be better off building your own project type. That allows you every configuration option. If the generic project type doesnt work an example like the emacs or linux project type would be the place to start.

Eric

Sent from Samsung tablet

Diez Roggisch <deets <at> web.de> wrote:

Hi there,

I'm using the CEDET 1.1 release with emacs 23 under OSX.

I'm interested in managing our existing (huge, own build-infrastructure)
C++-project using EDE.

I want to

- persist settings as current wordsize for build (32/64 bit), target
(debug/release) and various other settings such as running/debugging in
specific modes
- setup semantic, possibly using clang, for code-completion and
source-code navigation

I thought that ede-simple-project would be best, because cpp-root-project
isn't suitable (or can it store values such as wordsize or target
dynamically, not in the .emacs?). But when I invoke ede-new, I'm only
offered

ANDROID ROOT ARDUINO SKETCH
Automake GNUstep-Make
GNUstep-Make in scanner mode GNUstep-make Top Most
Make

No simple.

Any suggestions?

Thanks,

Diez

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
cedet-semantic mailing list
cedet-semantic <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-semantic

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
cedet-semantic mailing list
cedet-semantic <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-semantic

headers

Eric Ludlam | 27 Jun 2012 15:36

Re: ede-simple-project - how to? and some other questions

Hi,

EDE is setup for automatic detection and generic projects can get in the way so you need to enable them explicitly. You probably don't need all the simple ones provided. You would put:

(require 'exe-generic)

Into your .emacs and follow that with a command similar to those at the end of ede-generic.el, but with your build config file and build/debug commands.

I don't have access to my dev machine this week so I can't draft examples at the moment. Sorry.

Eric

Sent from Samsung tablet

Diez Roggisch <deets <at> web.de> wrote:

Hi,

The ede-simple project type was deprecated. It shouldn't be in any of the distributions anymore either. Perhaps there are other references around we still need to get rid of? The replacement would be the generic project type. The examples are at the end of the ede generic.el file. It will let you persist some changes to build and debug commands..

If your large codebase has others who will be sharing your work you will be better off building your own project type. That allows you every configuration option. If the generic project type doesnt work an example like the emacs or linux project type would be the place to start.

First of all a disclaimer: I'm a Emacs/Lisp-noob.

The generic project type looks like a good starting point. However, when I go e.g. Into ielm, I find that with the exception of ede-generic-load none of the definitions of ede-generic.el is found. I use CEDE1.1 release version, and after re-reading the INSTALL file again installed it like this in my .emacs:

(custom-set-variables ….)

(global-font-lock-mode t)

;; CEDET

(load-file "/Users/dir/.emacs.d/lib/cedet-1.1/common/cedet.el")

(global-ede-mode 1)

Any suggestions? Should I switch to the latest VCS version?

Also, again a question regarding building: as mentioned, my goal is to build for various targets/architectures. I guess this means that I update the project's build-command when the parametrization changes, and that's persisted somehow?

Thanks for you support,

Diez

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
cedet-semantic mailing list
cedet-semantic <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-semantic

headers

Diez Roggisch | 14 Aug 2012 11:39

Re: ede-simple-project - how to? and some other questions

Hi,

EDE is setup for automatic detection and generic projects can get in the way so you need to enable them explicitly. You probably don't need all the simple ones provided. You would put:

(require 'exe-generic)

Into your .emacs and follow that with a command similar to those at the end of ede-generic.el, but with your build config file and build/debug commands.

I don't have access to my dev machine this week so I can't draft examples at the moment. Sorry.

I had a look and it seemed to me as if the generic project pretty much relies on a single File that exists, e.g. A Makefile. We don't have such a thing, instead our project layout is like this:

Root/

Where all these are directories, and the A/B/C also are essentially build-targets.

Can I make this work with ede-generic?

Regards,

Diez

Hi,

The ede-simple project type was deprecated. It shouldn't be in any of the distributions anymore either. Perhaps there are other references around we still need to get rid of? The replacement would be the generic project type. The examples are at the end of the ede generic.el file. It will let you persist some changes to build and debug commands..

If your large codebase has others who will be sharing your work you will be better off building your own project type. That allows you every configuration option. If the generic project type doesnt work an example like the emacs or linux project type would be the place to start.

First of all a disclaimer: I'm a Emacs/Lisp-noob.

The generic project type looks like a good starting point. However, when I go e.g. Into ielm, I find that with the exception of ede-generic-load none of the definitions of ede-generic.el is found. I use CEDE1.1 release version, and after re-reading the INSTALL file again installed it like this in my .emacs:

(custom-set-variables ….)

(global-font-lock-mode t)

;; CEDET

(load-file "/Users/dir/.emacs.d/lib/cedet-1.1/common/cedet.el")

(global-ede-mode 1)

Any suggestions? Should I switch to the latest VCS version?

Also, again a question regarding building: as mentioned, my goal is to build for various targets/architectures. I guess this means that I update the project's build-command when the parametrization changes, and that's persisted somehow?

Thanks for you support,

Diez

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
cedet-semantic mailing list
cedet-semantic <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cedet-semantic

headers

Eric M. Ludlam | 29 Aug 2012 02:51

Re: ede-simple-project - how to? and some other questions

On 08/14/2012 05:39 AM, Diez Roggisch wrote:
> I had a look and it seemed to me as if the generic project pretty much
> relies on a single File that exists, e.g. A Makefile. We don't have such
> a thing, instead our project layout is like this:
>
>
> Root/
>     A/
>     B/
>     C/
>
>
> Where all these are directories, and the A/B/C also are essentially
> build-targets.
>
> Can I make this work with ede-generic?

Hi Diez,

   Sorry for the late reply.

   I suspect that you just need to use ede-cpp-root project type.  It is 
described in the manual.  In that case you would just add something to 
your .emacs file that says exactly where your projects are.

   If you still need to have an autodetect scheme, think about your 
project.  Does it always have a home grown build file, like 
MyBuildFile.py or something?  If so, you can create your own generic 
project type.  In ede/generic.el look at the end for how scons or cmake 
is defined.  Copy one of those, and you'll be ready to go.   Each 
definition is perhaps 12 lines of code, most of it is just declarative 
stuff.

   Generic projects can run into problems if not every directory has a 
build file.  In that case, you probably need the cpp-root project, and 
perhaps some home-grown setup.

Eric

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/