The Following User Says Thank You to RCL For This Useful Post: | ||
![]() |
2010-05-22
, 12:37
|
Posts: 13 |
Thanked: 3 times |
Joined on May 2010
@ Russian working in Poland for an US company :)
|
#3
|
![]() |
2010-05-22
, 18:03
|
Posts: 190 |
Thanked: 129 times |
Joined on Mar 2010
@ Bavaria, Germany
|
#4
|
o2_germany.o: o2_germany.cpp o2_germany.hpp \ ../providerinterface.hpp \ ../contactinfo.hpp \ ../export.hpp \ ../providerplugin.hpp \ ../accountsettingsdialog.hpp \ o2_germany.moc $(CXX) -c $(CXXFLAGS) $(INCPATH) -o o2_germany.o o2_germany.cpp
![]() |
2010-05-23
, 11:44
|
Posts: 13 |
Thanked: 3 times |
Joined on May 2010
@ Russian working in Poland for an US company :)
|
#5
|
![]() |
2010-05-23
, 13:17
|
Posts: 190 |
Thanked: 129 times |
Joined on Mar 2010
@ Bavaria, Germany
|
#6
|
![]() |
2010-05-24
, 11:51
|
Posts: 62 |
Thanked: 97 times |
Joined on Dec 2009
@ Finland, Kerava
|
#7
|
The Following 2 Users Say Thank You to rontti For This Useful Post: | ||
![]() |
2010-05-25
, 10:27
|
Posts: 13 |
Thanked: 3 times |
Joined on May 2010
@ Russian working in Poland for an US company :)
|
#8
|
I've never added "../" to HEADERS.
In my opinion there is no reason to do this. If you want to use the code of a directory "upper", make a shared/static library of them. On this way you also see the headers and sources.
If you don't like that solution, create a "whatever.pri" which contains "HEADERS += $$PWD/header.h" and in your project which is using it add "include(../../../whatever/whatever.pri)"
/libraries/ /math /utilities /objects ... /projects/ /maemo ... (maemo projects) /pc ... (pc projects) /ps3 ...
By the way: If you ONLY add headers which don't even contain Q_OBJECT macros, this is just for beauty and doesn't mean anything for the compiler. (I suppose you know that)
![]() |
2010-05-28
, 11:24
|
|
Posts: 122 |
Thanked: 135 times |
Joined on Dec 2009
@ Helsinki
|
#9
|
The Following User Says Thank You to too For This Useful Post: | ||
![]() |
2010-06-01
, 15:09
|
Posts: 13 |
Thanked: 3 times |
Joined on May 2010
@ Russian working in Poland for an US company :)
|
#10
|
Building debugging helper library in D:/RCL/local/MADDE/0.6.72/sysroots/fremantle-arm-sysroot-10.2010.19-1-slim/usr/share/qt4/qtc-debugging-helper/ Running D:/rcl/local/madde/0.6.72/bin/make.exe distclean... make: *** No rule to make target `..\mkspecs\default\qmake.conf', needed by `Makefile'. Stop. Running d:/rcl/local/madde/0.6.72/targets/fremantle-pr12/bin/qmake.exe ... Running D:/rcl/local/madde/0.6.72/bin/make.exe ... make: *** No rule to make target `..\mkspecs\default\qmake.conf', needed by `Makefile'. Stop.
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.