blackberry / Qt

A popular cross-platform application framework
72 stars 23 forks source link

How to specify the target for application in the QT Creator? #15

Open micrcx opened 12 years ago

micrcx commented 12 years ago

I installed on my laptop under Windows 7 QT for BB Playbook and QT Creator and was able to create and build the simple project.

14:25:38: Running steps for project First... 14:25:38: Starting: "C:\bbndk-2.0.0\host\win32\x86\usr\bin\make.exe" clean -w make.exe: Entering directory C:/BBQt/First' rm -f moc_mainwidget.cpp rm -f ui_mainwidget.h rm -f main.o mainwidget.o moc_mainwidget.o rm -f *~ core *.core make.exe: Leaving directoryC:/BBQt/First' 14:25:40: The process "C:\bbndk-2.0.0\host\win32\x86\usr\bin\make.exe" exited normally. 14:25:40: Configuration unchanged, skipping qmake step. 14:25:40: Starting: "C:\bbndk-2.0.0\host\win32\x86\usr\bin\make.exe" -w make.exe: Entering directory C:/BBQt/First' c:/QtPlaybookSDK/Playbook/Qt/4.8.1/bin/uic.exe mainwidget.ui -o ui_mainwidget.h qcc -Vgcc_ntoarmv7le -lang-c++ -c -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/mkspecs/default -I. -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtCore -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtGui -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include -I. -I. -I../../bbndk-2.0.0/target/qnx6/usr/include -I../../bbndk-2.0.0/target/qnx6/usr/include/freetype2 -o main.o main.cpp qcc -Vgcc_ntoarmv7le -lang-c++ -c -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/mkspecs/default -I. -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtCore -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtGui -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include -I. -I. -I../../bbndk-2.0.0/target/qnx6/usr/include -I../../bbndk-2.0.0/target/qnx6/usr/include/freetype2 -o mainwidget.o mainwidget.cpp C:/QtPlaybookSDK/Playbook/Qt/4.8.1/bin/moc.exe -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/mkspecs/default -I. -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtCore -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtGui -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include -I. -I. -I../../bbndk-2.0.0/target/qnx6/usr/include -I../../bbndk-2.0.0/target/qnx6/usr/include/freetype2 -D__QNXNTO__ mainwidget.h -o moc_mainwidget.cpp qcc -Vgcc_ntoarmv7le -lang-c++ -c -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/mkspecs/default -I. -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtCore -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include/QtGui -I../../QtPlaybookSDK/Playbook/Qt/4.8.1/include -I. -I. -I../../bbndk-2.0.0/target/qnx6/usr/include -I../../bbndk-2.0.0/target/qnx6/usr/include/freetype2 -o moc_mainwidget.o moc_mainwidget.cpp qcc -Vgcc_ntoarmv7le -lang-c++ -Wl,-rpath-link,C:/bbndk-2.0.0/target/qnx6/armle-v7/lib -Wl,-rpath-link,C:/bbndk-2.0.0/target/qnx6/armle-v7/usr/lib -Wl,-O1 -o First main.o mainwidget.o moc_mainwidget.o -LC:/bbndk-2.0.0/target/qnx6/armle-v7/lib -LC:/bbndk-2.0.0/target/qnx6/armle-v7/usr/lib -LC:\QtPlaybookSDK\Playbook\Qt\4.8.1\lib -lQtGui -L/home/andy/playbook/qt/stage/Playbook/Qt/4.8.1/lib -L/opt/bbndk-2.0.0-beta2/target/qnx6/armle-v7/lib -L/opt/bbndk-2.0.0-beta2/target/qnx6/armle-v7/usr/lib -lQtCore -lm make.exe: Leaving directoryC:/BBQt/First' 14:25:56: The process "C:\bbndk-2.0.0\host\win32\x86\usr\bin\make.exe" exited normally. 14:26:11: No hostname specified for device Error while building/deploying project First (target: QNX Arm) When executing step ''

The problem arose during deployment because I must define the target device (in my case it's 192.168.2.100). I know how make it in QNX Momentics IDE. How I've should be make this in QT Creator?

ghost commented 12 years ago

In QtCreator, Tools>Options>Linux devices (bottom left corner) and add your PlayBook device. Same as in Momentics IDE, although you must manually create debug token.

rafaelroquetto commented 12 years ago

@micrcx did you manage it? Is this still an issue for you?