Missing deploy to remote linux in qtcreator
-
Hi,
I installed qtcreator using the ubuntu software center, and set up a toolchain based on our embedded device. I'm unable to make a embedded project. I do not have an option for deploying to remote linux devices and I'm not sure how to "add" the option to my projects settings.
-
Which version of creator are you using? We keep changing that (let's hope things will stay stable for a while after 2.6).
-
I'm using 2.4.1,
I'm not sure if this helps, when I select my qt library that was built with the tool chain it says cannot detect ABI version. And when I create a project it only lets me select desktop
-
Ah, ok slightly further along, apparently I also needed a package that had minigw for embedded devices to even get the option. But I still can't add my qt version as an embedded build, it still is only selectable as a desktop version
-
I would recommend trying a Qt Creator 2.6 beta build... (or better yet a nightly). We are getting close to a release, so the nightly builds are rather stable, I use them for daily work. A lot has improved especially when it comes to working with devices (the remote linux desktop is counted as a device, too).
If a unreleased version is not an option for you at least get version 2.5.2.
-
OOOh thanks, 2.6 has options for sysroots, Now if I can just get it to work...
I have sdk's for armv5 and armv7 and I'm having a hard time adding the qt versions properly
-
IIRC we only offered the embedded linux uf the Qt version would not work on the desktop in Qt Creator 2.4... and had the sysroot hidden away in the Qt version (only if it did not possibly work on the desktop).
-
Ok i've got everything building in 2.6, unfortunately now that I've been able to configure a deployment method. I can't seem to configure what to deploy...
It just says Don't know what to run under Run, and there doesn't seem to be an option to add files to "local file path, remote directory" table
-
That is extracted from the .pro file. You need to define what to deploy to where there.
We want users to be able to build outside creator just as well as inside creator. So the deployment has to be handled by the build system, not creator.
-
Even deploying the created binary file? Thats not included in the deployment right now, i'm not sure how to get it to the device without copying it manually
@QT += core gui
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
TARGET = remote
addFiles.sources = remote
addFiles.path = /usr/binDEPLOYMENT += addFiles
TEMPLATE = appSOURCES += main.cpp
mainwindow.cppHEADERS += mainwindow.h
FORMS += mainwindow.ui@