Important: Please read the Qt Code of Conduct -

Deployment in Ubuntu Linux

  • I have a couple questions about deployment in Ubuntu. I have my application almost complete and I am looking into deployment options. I know there is two different types of deployment (static and dynamic), where static contains all the library files needed from Qt, and dynamic is the opposite.

    I have successfully brought my Linux application to another Linux box and installed using qmake and make (auto-tools). What I would really like to do is make my installation a .deb file, so I can install it in one shot with a .deb file (I'm assuming this will bring up the software center as well if I understand it correctly?)

    Unfortunately, I cannot find any tutorials on how to make a Qt4 application install via .deb file. I would like to make it a static install as well since all the box's will be used on might not have the Qt4 development environment pre-installed.

    Any one have any good tips on where to start?

    p.s. I have read many documents on how to make a .deb file, yet none give a step by step process on how to do so, just looking to automate the installation process for qmake and make, and all that good stuff. Also, this application might be used on a windows platform as well, but that's another by it's self.

  • Try discussing that with the debian packagers, #debian-qt-kde on OFTC.

  • I'm not sure you should go with static linking when creating .deb package. You simply can write qt as dependency and it will be installed automatically.

  • Moderators

    I know that creator is capable of generating all the magic that needs to happen to package a .deb for Harmattan & such. You might consider generating a skeleton app for that platform and looking at what the .pro looks like and what files are generated, and what the packaging deployment step looks like under Projects->Run. From there it might not be a big deal to change it to deal with Ubuntu. But that's just speculation. I'm not sure if there's other magic involved or not.

  • Thank you all for your input, previously I looked into adding the Qt dependencies on the install for .deb, I believe that would be the best way to go. I just gotta figure out how to do it! I believe its just an addition to the dependency list in the config file for the .deb package.

    I thank you all again for you input.

  • I have found the easiest Debian packaging guide (and it works perfectly for my own released app): Actually it is for Java (and my app is Java) but I can use it on my Qt app. Same.

Log in to reply