I ran some tests against EDE for C++ projects, and checked in
several fixes over the past week.
The LD libs variable in the compiled object entry is actually
targetted against the Automake style project, where those flags are
put into the LDADD Automake configuration item. The flags variable
doesn't seem be used still. :(
I've tested against the Automake target, and fixed a few bugs there,
so that system seems to be working well now. That direction may be
preferable as it will be more robust across different platforms.
You can convert an existing makefile project into a maiefle.am
project via 'customize-project' command.
>>> Alexander Syrov <asyrov@...> seems to think that:
>On Mon, 11 Apr 2005 14:55:14 -0400
>Eric M. Ludlam wrote:
> EML> Unfortunately, it is suffering from a bit of "you can't get there
> EML> from here" as those flags need to be merged with the flags from the
> EML> compiler definition. I don't have a good notion for fixing it at this
> EML> moment. It's a bit of a leftover from before I abstracted out the
> EML> compilers and linkers.
> EML> You could add your custom flags to any costom compiler/linkers you may
> EML> have.
>Probably I'll have to dig into EDE sources a bit deeper as I need this
>feature for my projects. I may create different linkers for different flags,
>but additional libraries are project- and not linker-specific. I'll post an
>article to this list if I'll find a solution.
>However, thanks for clarifying the situation.
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org