Bug 76013 - qmake project: run 'qmake' before make
Summary: qmake project: run 'qmake' before make
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: Build tools: QMake (show other bugs)
Version: 3.0.1
Platform: Compiled Sources Solaris
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-24 13:48 UTC by Daniel Franke
Modified: 2004-02-27 11:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Franke 2004-02-24 13:48:04 UTC
Version:           3.0.1 (using KDE 3.1.4)
Installed from:    compiled sources
Compiler:          gcc version 3.2.2
OS:          SunOS (sun4u) release 5.8

When moving projects between platforms, it may occur that qt is located in different places, e.g. '/usr/lib/qt3' (host1) and 'usr/local/qt3' (host2). Therefore running 'make' on a Makefile created on host1 may fail on host2:

--
* cd /tmp/sibsimbuilder && QTDIR="/usr/local/qt3" gmake -k  
* gmake: *** No rule to make target `/usr/lib/qt3/mkspecs/default/qmake.conf', needed by `Makefile'. 
* gmake: Failed to remake makefile `Makefile'. 
* gmake[1]: *** No rule to make target `/usr/lib/qt3/mkspecs/default/qmake.conf', needed by `Makefile'. 
* gmake[1]: *** No rule to make target `/usr/lib/qt3/lib/libqt-mt.prl', needed by `Makefile'. 
* gmake[1]: Failed to remake makefile `Makefile'.
[...]
--

Running qmake prior to (g)make solves this.

BTW: these make errors aren't highlighted as compile errors are (red)?!
Comment 1 Daniel Franke 2004-02-25 18:30:50 UTC
Giving this some more thought, I believe this report should be closed as INVALID, since no one expects an automake project to work when moving it around after running 'configure'. In an automake based project one has to re-configure to get it working again - corresponding to run 'qmake' after moving a qmake based project ...
Comment 2 Amilcar do Carmo Lucas 2004-02-27 11:00:42 UTC
Like he said, the user should do it. It's not our job to do it.