Bug 245820 - Automake editor is not handling automake if/else constructs
Summary: Automake editor is not handling automake if/else constructs
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-cdt
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnston
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-26 20:41 UTC by Jeff Johnston
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-06-26 21:24:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeff Johnston 2007-06-26 20:41:15 UTC
When editing Makefile.am files, if/else constructs interfere with parsing logic.
 For example,

all: hello.c
if USE_GCC
\tgcc hello.c
else
\tcc hello.c

In this case, the outline should either show the gcc command or the cc command.
 In addition, in the processed Makefile.in files, the processed if statements
(@cond@) are not being recognized as target rules.  For example:

all: hello.c
@USE_GCC_TRUE@\tgcc hello.c
@USE_GCC_FALSE@\tcc hello.c

This causes the editor to not treat the two commands as commands for the all target.

Comment 1 Jeff Johnston 2007-06-26 21:24:17 UTC
Fixed in current repository.  Automake if/else is evaluated and statements are
either handled or ignored (currently conditions are defaulted to false).  A
patch also supports the Makefile.in processed statements so they are treated
properly.  There is no ignoring of Makefile.in statements and the prefixes are
shown in the outline view.


Note You need to log in before you can comment on or make changes to this bug.