Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt Creator and other tools
  4. How to automatically setup deploy steps for remote device
Forum Updated to NodeBB v4.3 + New Features

How to automatically setup deploy steps for remote device

Scheduled Pinned Locked Moved Solved Qt Creator and other tools
4 Posts 3 Posters 384 Views 2 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.
  • S Offline
    S Offline
    SebastianM
    wrote on 5 Sept 2024, 07:58 last edited by SebastianM 9 May 2024, 07:59
    #1

    I'm using sdktool to successfully setup cross-compilation kit (Qt 6.5).
    I've got set of 6 steps (Run custom remote command,Install into temporary host directory and Custom process step).
    I would like those steps to set automatically also (like kit configuration).
    Yet, I failed to find command to do so.
    I found something useful in <MY_PRJ_SOURCE_DIR>/CMakeLists.txt.user (xml format). I may have to do modify it manually (or with eg. xmlstarlet)
    Can I do it in any other way? More robust?

    A 1 Reply Last reply 5 Sept 2024, 17:02
    0
    • S SebastianM
      5 Sept 2024, 07:58

      I'm using sdktool to successfully setup cross-compilation kit (Qt 6.5).
      I've got set of 6 steps (Run custom remote command,Install into temporary host directory and Custom process step).
      I would like those steps to set automatically also (like kit configuration).
      Yet, I failed to find command to do so.
      I found something useful in <MY_PRJ_SOURCE_DIR>/CMakeLists.txt.user (xml format). I may have to do modify it manually (or with eg. xmlstarlet)
      Can I do it in any other way? More robust?

      A Offline
      A Offline
      artwaw
      wrote on 5 Sept 2024, 17:02 last edited by
      #2

      @SebastianM wrap it all into the script, call the script from the cmake or add the build step?

      For more information please re-read.

      Kind Regards,
      Artur

      S 1 Reply Last reply 11 Sept 2024, 09:06
      1
      • I Offline
        I Offline
        Isabella Marie
        wrote on 6 Sept 2024, 13:03 last edited by
        #3
        This post is deleted!
        1 Reply Last reply
        0
        • A artwaw
          5 Sept 2024, 17:02

          @SebastianM wrap it all into the script, call the script from the cmake or add the build step?

          S Offline
          S Offline
          SebastianM
          wrote on 11 Sept 2024, 09:06 last edited by
          #4

          @artwaw That sound like a solid solution. Thank you.
          Script as file in repository or CMake target set to run AFTER build is completed.
          I struggled a little with CMake target approach - as by default - Qt Creator set flag Stage for installation which is not accessible by CMake. Still - unmark manually by user is far easier then setup 6 deploy steps in GUI.

          XML approach I rejected as too big (~40 XML lines where most of them are just copy-paste) and too brittle (file ~/.config/QtProject/qtcreator/profiles.xml).

          1 Reply Last reply
          0
          • S SebastianM has marked this topic as solved on 11 Sept 2024, 12:08

          1/4

          5 Sept 2024, 07:58

          • Login

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