Re: [CEDET-devel] No idea how to make a simple EDE project

[Eric M. L. <eri...@gm...>]

Hi,

You are right about this deficiency.  That sort of doc has been lacking 
from what is currently written as a reference.  I added a quickstart 
section to the EDE manual which basically mimics a subset of one of the 
tests.  I followed the documented steps and it works for me, and the 
test is a bit more complex, and continues to work.  Perhaps this doc 
will prove useful?

Here is a link from the build-bot doc:

http://www.randomsample.de/cedetdocs/ede/ede/Quick-Start.html

If something doesn't make sense, let me know and I'll update it.

For you specific question on the dependencies, I think if you tell 
Automake about the dependencies using the ldlibs-local variable in EDE, 
Automake just figures it out.  Either that, or I've just been lucky so far.

Thanks
Eric

On 02/23/2012 03:20 PM, Mike Boyle wrote:
> I've been trying for days to get a simple EDE project to compile
> sensibly, but it just won't work without a lot of ugly hacking. I've
> searched the entire internet by now, but all I can find is the
> impenetrable EDE documentation, which I'm just not smart enough to
> figure out. Judging from other people's questions on stackoverflow, I'm
> not alone. Please help walk me through this (and don't just tell me M-x
> customize-project will solve all my problems, because it doesn't).
>
> Say I've got a project like
> NewProject/
> main.cpp
> functions/
> function1.cpp
> function1.h
> function2.cpp
> function2.h
> where main.cpp just includes function*.h and uses the simple functions
> declared therein. So I have a top-level EDE project and a subproject,
> each of type Make. The subproject has a target 'functions' of type
> 'sharedobject', with the two cpp files as the source files. The
> top-level project has a target 'main' of type 'program' with main.cpp as
> the source file. How do I have the project first compile the functions
> library, and only then compile and link main.cpp?
>
> More generally, is there a way to make a target just call another target
> from a subproject?
>
> Also, is there a more elegant way of including the sharedobject library
> when linking main? Up to now, I've just been editing the main target and
> setting the ldflags to '-Lfunctions -lfunctions'. This seems a bit
> hackish to me. For example, if I put functions/libfunctions.la into
> Ldlibs-Local, this just affects the dist target. It seems like it should
> add a dependency, and include it when linking main.
>
> Thanks for your help.
>
> Mike
>
>
>
> ------------------------------------------------------------------------------
> 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