Bug 245820 - Automake editor is not handling automake if/else constructs
Automake editor is not handling automake if/else constructs
Product: Fedora
Classification: Fedora
Component: eclipse-cdt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnston
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-06-26 16:41 EDT by Jeff Johnston
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-26 17:24:17 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Johnston 2007-06-26 16:41:15 EDT
When editing Makefile.am files, if/else constructs interfere with parsing logic.
 For example,

all: hello.c
\tgcc hello.c
\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 17:24:17 EDT
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.