Hi Eric,
Thanks for your reply.
Well I can make the project work to a degree, but I don't know how to
adapt it to my configuration. For example, it's fairly easy to get a
project to work when all of the source files are in the same directory
as the Project.ede file, but this is not the configuration I am forced
to work under. In my case, the project's include files are in there
own '/inc' directory and the source files are in there own '/src'
(Project.ede in the root directory). I understand that it is possible
to change the :path argument to point to the directory of the source
files, but this does not appear to make any difference to the final
makefile. Also, how do I add an include directory?
If I attempt to execute customize-target, the system returns: "Wrong
type argument: eieio-object-p, nil". I have had this problem before.
If I run "rescan project files" anything I do from that point onwards
returns "Wrong type argument: (or eieio-object-p class-p), nil". To
recover, I need to restart my Emacs.
Thanks for your help,
Steve
On Fri, Nov 27, 2009 at 2:05 PM, Eric M. Ludlam <eric@...> wrote:
> Hi,
>
> I'm going to guess that you are trying to hand-write the Project.ede file?
> While I suppose that is doable, as it is just a Lisp data structure, I have
> not done so. The best way to create a project is with the command
>
> M-x ede-new RET
>
> You then create a target with "C-c . t" to add a target or two.
>
> Next, you could flip into DirEd mode, and mark a bunch of files, and use ".
> a" to add all those files into some target.
>
> Next, use M-x customize-target RET while inside some source file in a target
> to customize things like compiler flags.
>
> Each stepp will save up an updated Project.ede file with the correct syntax.
>
> There is a different project project where, as far as I know, you need to
> hand write the project file, and the syntax with colon based :keywords is
> very similar looking, but that is not EDE.
>
> The Emacs crashing business is interesting though. I'm not sure if that is
> related to tramp or not. I hadn't tried using TRAMP and EDE together.
>
> Good Luck
> Eric
>
> Stephen Henry wrote:
>>
>> Hi all,
>>
>> I am a new CEDET user and I am desperately trying to get it to work
>> for my next big piece of work (as the functionality would come in
>> really handy and it would allow me to remain in an emacs environment,
>> which would be good). It's at the stage were nothing is working at
>> all, (Emacs even crashes quite regularly when attempting to load a
>> simple Project.ede file). I believe that CEDET is installed okay, as
>> the modifications to the EMACS file are fairly straight forward and
>> all of the 'require' statements appear to be succeeding.
>>
>> This is what I'm trying to do:
>>
>> I have fairly standard c++ project consisting of the following
>> directory structure.
>>
>> Project.ede
>> ./src - (containing the programs source code)
>> ./src/main.cpp
>> ./inc - (containing the programs header files)
>>
>> I would like to define a Project.ede file, that would effectively
>> allow me to build and manage everything I need from Emacs (along with
>> autocompletion, intelligent search, etc...)
>>
>> In Project.ede, I have written the following (although I have some
>> considerable difficulty finding any documentation on how the
>> Project.ede file is actually structured).
>>
>> (ede-proj-projet "MTCAS"
>> :name "MTCAS"
>> :file "Project.ede"
>> :targets (list
>> (ede-proj-target-makefile-program "arcsim"
>> :name "arcsim"
>> :path "./src"
>> :source '("main.cpp")
>> :ldlibs '("ELFIO")))
>>
>> I've really tried to keep it as simple as possible (but to no avail -
>> actually, that code crashes my emacs!). Obviously, it would be nice to
>> use elisp to automatically calculate the sources by using
>> (directory-files "./src" nil "*.cpp" nil), but first-things-first.
>>
>> So I guess what I'm trying to ask is:
>>
>> 1. Given a standard c++ project, how can one make a EDE project for it
>> (where is the documentation telling one how to do this. I've seen the
>> blog posting, but that isn't really detailed enough to help me)
>>
>> 2. Are there any procedures that I can call that will give me better
>> visibility into the crashes and allow me to debug them?
>>
>> 3. Is CEDET mature enough to start using on a new project (or should I
>> look at Eclipse or Xcode as an alternative)?
>>
>> I am running a non-standard configuration. My project is located on a
>> remote server, and I log into it using TRAMP over SSH. I am using
>> emacs 23.1 on a Macbook Pro running Snow leopard.
>>
>> Any help would be appreciated,
>>
>> Steve
>>
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day trial. Simplify your report design, integration and deployment - and
>> focus on what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Cedet-devel mailing list
>> Cedet-devel@...
>> https://lists.sourceforge.net/lists/listinfo/cedet-devel
>>
>
|