Bug 245820

Summary: Automake editor is not handling automake if/else constructs
Product: [Fedora] Fedora Reporter: Jeff Johnston <jjohnstn>
Component: eclipse-cdtAssignee: Jeff Johnston <jjohnstn>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-06-26 21:24:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.