[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 150721] New: Makefile settings aren't always correctly handled
From: Jeroen Dierckx <jeroen.dierckx () gmail ! com>
Date: 2007-10-11 15:50:37
Message-ID: 20071011175036.150721.jeroen.dierckx () gmail ! com
[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=150721
Summary: Makefile settings aren't always correctly handled in the
qmake manager
Product: kdevelop
Version: 3.5.0
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Build tools: QMake
AssignedTo: kdevelop-bugs kdevelop org
ReportedBy: jeroen.dierckx gmail com
Version: 3.5.0 (using KDE 3.5.7, Kubuntu (gutsy) 4:3.5.7-1ubuntu15)
Compiler: Target: i486-linux-gnu
OS: Linux (i686) release 2.6.22-14-generic
In our linux build environment, we use a common .pri file that we include in all our \
projects. As we have all our .pro files in one directory, we use custom Makefile \
names. The MAKEFILE setting is set in the common.pri file as "MAKEFILE = \
Makefile.$${TARGET}". There are two problems with this:
1. Kdevelop doesn't use the inherited MAKEFILE setting. When building the project, it \
tries to build using the standard Makefile 2. When using the same setting in the \
actual project file (so putting the "MAKEFILE = Makefile.$${TARGET}" there), kdevelop \
literally tries to run "make -f Makefile.$${TARGET}", which obviously fails. So \
probably not that trivial, but the qmake variables should be substituted (kdevelop \
should run "make -f Makefile.MyProject").
_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic