Cross-platform best practice?

Comments

3 comments

  • Avatar
    jesus

    Hi Niels,

    Our recommendation is using a single platform to build the installers for each platform. Also, in order to avoid copying all those data in each build, we suggest you having all the necessary data in the machine that will generate the installers.

    0
    Comment actions Permalink
  • Avatar
    rturrentine

    I am facing the same question. I'm evaluating InstallBuilder for use with my cross platform, Qt based desktop application. Currently I use another opensource install tool for Windows and then use shell scripts to generate RPMs on Linux and PKGs on Solaris.

    Since the binary files are different for each OS, I'm not seeing a great advantage of using a single InstallBuilder project across all platforms. There could be times when a release is only done on one operating system (I try to avoid it though).

    0
    Comment actions Permalink
  • Avatar
    Niels Holst

    Thanks, rturrentine, I was beginning to wonder whether I was making this more complicated than it is. It seems we agree that building installers across platforms can be a headache, even with the assistance of InstallBuilder (not that I would like to try to do it without).

    I have ended up with three boxes (Linux, OS X, Windows). Qt Creator is installed on all three and so is InstallBuilder. A GitHub project keeps source code (including the InstallBuilder XML project file) current; it is the exact same in all three boxes. However, I could not find out to code a qmake script that would build the source, assign version numbers and run InstallBuilder automatically across platforms. So, I have written a build script, one for each platform, to build from source the platform-specific installer file.

    0
    Comment actions Permalink

Please sign in to leave a comment.