Creator: "run" not finding shared library
-
wrote on 15 Mar 2011, 13:11 last edited by
*= is valid, Gerolf. It will add to the variable only if the added value is not already contained. I use it all the time. It is especially handy if you use .pri files that might get included more than once.
-
wrote on 15 Mar 2011, 13:20 last edited by
Note that my previous use of
SOURCES += *.cpp
HEADERS += *.hseemed to work. I have also used:
SOURCES += $$system(ls $$(VALUE_HOME)/libvalutil/src/*.cpp
and similar lines successfully on one of my original, non-Creator projects.
-Tom
-
wrote on 15 Mar 2011, 13:24 last edited by
Creator just calls qmake and make and does not fiddle around in the project files and does not construct compiler command lines itself.
If you .pro works on the command line, it works in Creator too.
-
wrote on 15 Mar 2011, 13:29 last edited by
[quote author="Volker" date="1300195458"]Creator just calls qmake and make and does not fiddle around in the project files and does not construct compiler command lines itself.
[/quote]
But Creator does fiddle around with command line arguments and environment variables. Those too can influence your endresult!
[quote]
If you .pro works on the command line, it works in Creator too.[/quote]
So the above is not entirely true. -
wrote on 15 Mar 2011, 13:48 last edited by
Creator adds command line arguments to the qmake call (release/debug, mkspec and some defines for the QML debuger); for the actual build process it just calls "make -w" (you may add some additional arguments to make manually). The environment variables are just your regular environment when left in standard settings.
-
wrote on 15 Mar 2011, 13:55 last edited by
[quote author="Volker" date="1300196895"]Creator adds command line arguments to the qmake call (release/debug, mkspec and some defines for the QML debuger); for the actual build process it just calls "make -w" (you may add some additional arguments to make manually). The environment variables are just your regular environment when left in standard settings.[/quote]
Yes, that is correct, but it does mean that the same .pro file may result in different result when used unsuspectingly to build from the command line or from creator. I have actually encountered this. What's more, I even have some code that builds just fine if I build from the command line, but triggers a compiler exception if I start the build from Qt Creator. Beats me why, never been able to find out the cause.
-
wrote on 15 Mar 2011, 13:58 last edited by
[quote author="Andre" date="1300197353"]
Yes, that is correct, but it does mean that the same .pro file may result in different result when used unsuspectingly to build from the command line or from creator. I have actually encountered this. What's more, I even have some code that builds just fine if I build from the command line, but triggers a compiler exception if I start the build from Qt Creator. Beats me why, never been able to find out the cause.[/quote]
Wow... I never came across this. Very weird....
-
wrote on 15 Mar 2011, 14:42 last edited by
Andre and Volker, that may be similar to the problem I reported: the output from Creator is chopping the compiler command options and causing a make error, which could reflect a compiler exception since it is an unknown command to g++.
-
wrote on 15 Mar 2011, 15:02 last edited by
Make sure there's no hidden white space after the \ though.
-
wrote on 15 Mar 2011, 15:31 last edited by
[quote author="tbrowder" date="1300200176"]Andre and Volker, that may be similar to the problem I reported: the output from Creator is chopping the compiler command options and causing a make error, which could reflect a compiler exception since it is an unknown command to g++.[/quote]
Can you create a small sample project to demonstrate the effect?
Also, what's the command line which Creator calls on qmake? You can see it in the output tab of Creator.
27/27