[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 114801] New: Build Targets shows invalid targets after automatic makefile scanning
From:       kdevelop-bugs-admin () barney ! cs ! uni-potsdam ! de
Date:       2005-10-21 7:58:58
Message-ID: 20051021095857.114801.reinoud.bokhorst () met ! no
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=114801         
           Summary: Build Targets shows invalid targets after automatic
                    makefile scanning
           Product: kdevelop
           Version: 3.2.2
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: reinoud.bokhorst met no


Version:           3.2.2 (using KDE KDE 3.4.2)
Installed from:    Fedora RPMs
Compiler:          gcc 3.4.3 
OS:                Linux

I have my own custom makefile for use with GNU make. This makefile is automatically \
scanned by Kdevelop and the build targets show up under the Build -> Build Target \
menu.

My makefile contains variable declarations using this syntax:

varname := varvalue

GNU calls these "Simply expanded variables" i contrast to "recursively expanded \
variable" declared as:

varname = varvalue

In Kdevelop 3.1.1, these kind of variables were not considered to be valid targets \
(which is correct), in Kdevelop 3.2.2 they suddenly show up in the Build Target menu, \
which is wrong.

After changing the simply expanded variables to recursively expanded variables, they \
disappeared from the Build Target menu.


[prev in list] [next in list] [prev in thread] [next in thread]