Still working with tutorials...
-
If you want to continue on the command line then this "wiki article":http://developer.qt.nokia.com/wiki/Generate_Makefiles_instead_of_XCode_projects_on_Mac_OS_X will help you.
If you want to use Qt Creator, just open the .pro file in Creator, it runs qmake for you.
-
Really? Just opening the .pro file causes qmake to run?
Also, from one of the instructional videos (which might be out of date by now), I got the impression that one needed to run qmake, then run make. True or not?
I'm also curious: is it OK to go back and forth between a CLI and Creator for a particular project, or is it better to choose one and stick to it?
Thanks.
-
[quote author="mzimmers" date="1295304369"]
I'm also curious: is it OK to go back and forth between a CLI and Creator for a particular project, or is it better to choose one and stick to it?Thanks.[/quote]
It’s best to learn both. You can go around with only one. Your pick, and your timeline and interest what you actually want to accomplish :)
-
[quote author="Smar" date="1295304606"]
[quote author="mzimmers" date="1295304369"]
I'm also curious: is it OK to go back and forth between a CLI and Creator for a particular project, or is it better to choose one and stick to it?Thanks.[/quote]
It’s best to learn both. You can go around with only one. Your pick, and your timeline and interest what you actually want to accomplish :)[/quote]
What I meant was, for a particular project...is it best to use only one of the two interfaces, or can you flip-flop without repercussions? Put another way...is the CLI compatible with Creator and the other GUI tools?
Thanks.
-
[quote author="mzimmers" date="1295304369"]Really? Just opening the .pro file causes qmake to run?
Also, from one of the instructional videos (which might be out of date by now), I got the impression that one needed to run qmake, then run make. True or not?
I'm also curious: is it OK to go back and forth between a CLI and Creator for a particular project, or is it better to choose one and stick to it?
Thanks.[/quote]
Qt Creator calls qmake and make for you, captures the output and can bring you to the point in the code where the error happened.
It is perfectly ok to switch between CLI and Creator. Although you should keep in mind that the shadow builds, that Creator enables by default, reside in another directory. You should know what you're doing, otherwise you can mess up thing.
-
[quote author="mzimmers" date="1295304889"]
What I meant was, for a particular project...is it best to use only one of the two interfaces, or can you flip-flop without repercussions? Put another way...is the CLI compatible with Creator and the other GUI tools?
[/quote]Shortly: yes.
-
Shadow builds...that's a term I haven't come across yet. I assume that is for some default target that Creator keeps track of? I've done some tutorials that have resulted in subdirectories like tutorial6 AND tutorial6-build-desktop...is this what you're talking about? Oddly enough, it doesn't happen all the time.
Also, per the Wiki you cited above: I don't seem to have a mkspecs directory anywhere. Was I supposed to create this myself?
Thanks.
-
A shadow build is a build setup and cycle (creating intermediate and object files as well as the final executable or lib) in an directory outside your source tree.
Regarding the wiki article: You do have the dir somewhere, it's where your Qt libs are installed. The actual directory depends on your installation.
-
[quote author="Volker" date="1295307950"]Regarding the wiki article: You do have the dir somewhere, it's where your Qt libs are installed. The actual directory depends on your installation.
[/quote]I've done a search on my entire HD for a file/directory with that name...nothing. I wonder if I botched something in the installation?
-
[quote author="mzimmers" date="1295308733"]
I've done a search on my entire HD for a file/directory with that name...nothing. I wonder if I botched something in the installation?[/quote]No, it must be on your HD otherwise qmake would not work at all. You can try
@
locate mkspecs
@in the shell (CLI).
-
You want to generate XCode projects when you want to work with the XCode IDE.
