Thread
:
MADDE's qmake generates incorrect makefiles for Windows - where to file bug?
View Single Post
RCL
2010-05-22 , 12:17
Posts: 13 | Thanked: 3 times | Joined on May 2010 @ Russian working in Poland for an US company :)
#
1
Hi,
if .pro file contains sources in parent directories, e.g. like
HEADERS += ../../../whatever/header.h
then qmake for Windows (more exactly .madde/0.6.14/targets/fremantle-qt-0951/bin/qmake.exe) will generate a makefile which will have "native" Windows backslashes for header dependencies, e.g.
../build/whatever.o: ../../../whatever/whatever.cpp ..\..\..\whatever\header.h
The problem is, that make (also from MADDE) will understand the backslashes as escaped symbols and will refuse to build such a makefile (it won't find header.h). Manually replacing backslashes with slashes fixes the problem but it's an unfeasible solution.
It only happens on Windows MADDE setup, on Ubuntu everything is Ok (only slashes are used obviously). Windows native qmake (from QT SDK for PC) also handles such .pro files correctly, placing slashes in a makefile.
I know that MADDE is still BETA, but I would like to report a bug against that nevertheless just to let developers know.
If there's a better place for bugreports against MADDE, let me know, please.
Quote & Reply
|
The Following User Says Thank You to RCL For This Useful Post:
Larswad
RCL
View Public Profile
Send a private message to RCL
Find all posts by RCL