Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Use Qt creator to create remote linux application
Forum Updated to NodeBB v4.3 + New Features

Use Qt creator to create remote linux application

Scheduled Pinned Locked Moved Mobile and Embedded
5 Posts 3 Posters 9.1k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Micka38
    wrote on last edited by
    #1

    Hello,
    I'm having troubles to create a qt aplication with qt creator for remote linux devices.

    The problem is i can't set the target path in the run settings :
    remote directory : <no target path set>
    According to "Qt reference documentation":http://doc.qt.nokia.com/qtcreator-2.5/creator-deployment-maemo.html
    I know I must modifie the .pro file but .. how?
    I find on this forum the folowing solution (which does not work):
    add the following lines of the .pro file:
    @
    linux-* {
    target.path = /home/username/executable
    }
    @
    I also try to use the DEPLOYMENT, DESTDIR and DESTDIR_TARGET variables without results.
    ==> always "<no target path set>" in the Run settings ...
    Ragards,
    Mickael

    1 Reply Last reply
    0
    • E Offline
      E Offline
      Exeunt Omnes
      wrote on last edited by
      #2

      I'm having the same problem. The documentation is surprisingly vague, but I've found that:

      [CODE]
      linux-* {
      target.path = ssh://yourname@xxx.xxx.xxx.xxx/remote/directory
      INSTALLS += target
      }
      [/CODE]

      at least shows up in the target path. I haven't tried to deploy it yet, but it's a start!

      But see correction below!

      (Sorry, I'd have edited this post if I'd realised it was possible.)

      1 Reply Last reply
      0
      • E Offline
        E Offline
        Exeunt Omnes
        wrote on last edited by
        #3

        PS: I'm assuming it's an SSH connection. If not, change as appropriate, but the principle would be the same.

        1 Reply Last reply
        0
        • E Offline
          E Offline
          Exeunt Omnes
          wrote on last edited by
          #4

          Correction: You don't have to put the full path in 'target.path...'. Instead click the 'Manage device configuration' link. This brings up a very straightforward wizard which allows you to set up your connection details, including the file path.

          The .pro file entry can then be as simple as:
          [CODE]
          linux-* {
          target.path = ./
          INSTALLS += target
          }
          [/CODE]
          as the path is now in the device configuration.

          It worked first time!

          1 Reply Last reply
          0
          • E Offline
            E Offline
            eJinn
            wrote on last edited by
            #5

            [quote author="Exeunt Omnes" date="1340222214"]
            The .pro file entry can then be as simple as:
            [CODE]
            linux-* {
            target.path = ./
            INSTALLS += target
            }
            [/CODE]
            as the path is now in the device configuration.
            It worked first time![/quote]
            Thank you very much!!!
            It`s really worked!

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved