{"id":37987,"date":"2026-01-01T01:38:17","date_gmt":"2026-01-01T06:38:17","guid":{"rendered":"https:\/\/twiar.net\/?p=37987"},"modified":"2025-12-14T01:39:52","modified_gmt":"2025-12-14T06:39:52","slug":"via-hackaday-creating-user-friendly-installers-across-operating-systems","status":"publish","type":"post","link":"https:\/\/twiar.net\/2026\/01\/01\/via-hackaday-creating-user-friendly-installers-across-operating-systems\/","title":{"rendered":"via Hackaday: Creating User-Friendly Installers Across Operating Systems"},"content":{"rendered":"
\"\"<\/div>\n

After you have written the code for some awesome application, you of course want other people to be able to use it. Although simply directing them to the source code on GitHub or similar is an option, not every project lends itself to the traditional configure && make && make install<\/code>, with often dependencies being the sticking point.<\/p>\n

Asking the user to install dependencies and set up any filesystem links is an option, but having an installer of some type tackle all this is of course significantly easier. Typically this would contain the precompiled binaries, along with any other required files which the installer can then copy to their final location before tackling any remaining tasks, like updating configuration files, tweaking a registry, setting up filesystem links and so on.<\/p>\n

As simple as this sounds, it comes with a lot of gotchas, with Linux distributions in particular being a tough nut. Whereas on MacOS, Windows, Haiku and many other OSes you can provide a single installer file for the respective platform, for Linux things get interesting.<\/p>\n

<\/span><\/p>\n

Windows As Easy Mode<\/h2>\n

For all the flak directed at Windows, it is hard to deny that it is a stupidly easy platform to target with a binary installer, with equally flexible options available on the side of the end-user. Although Microsoft has nailed down some options over the years, such as enforcing the user\u2019s home folder for application data, it\u2019s still among the easiest to install an application on.<\/p>\n

While working on the NymphCast project<\/a>, I found myself looking at a pleasant installer to wrap the binaries into, initially opting to use the NSIS<\/a> (Nullsoft Scriptable Install System) installer as I had seen it around a lot. While this works decently enough, you do notice that it\u2019s a bit crusty and especially the more advanced features can be rather cumbersome.<\/p>\n

This is where a friend who was helping out with the project suggested using the more modern Inno Setup<\/a> instead, which is rather like the well-known InstallShield<\/a> utility, except OSS and thus significantly more accessible. Thus the pipeline on Windows became the following:<\/p>\n

    \n
  1. Install dependencies using vcpkg<\/a>.<\/li>\n
  2. Compile project using NMake and the MSVC toolchain.<\/li>\n
  3. Run the Inno Setup script to build the .exe<\/code> based installer.<\/li>\n<\/ol>\n

    Installing applications on Windows is helped massively both by having a lot of freedom where to install the application, including on a partition or disk of choice, and by having the start menu structure be just a series of folders with shortcuts in them.<\/p>\n

    The Qt-based NymphCast Player application\u2019s .iss<\/code> file<\/a> covers essentially such a basic installation process, while the one for NymphCast Server also adds the option to download a pack of wallpaper images, and asks for the type of server configuration to use.<\/p>\n

    Uninstalling such an application basically reverses the process, with the uninstaller installed alongside the application and registered in the Windows registry together with the application\u2019s details.<\/p>\n

    MacOS As Proprietary Mode<\/h2>\n

    Things get a bit weird<\/a> with MacOS, with many application installers coming inside a DMG image or PKG file. The former is just a disk image that can be used for distributing applications<\/a>, and the user is generally provided with a way to drag the application into the Applications<\/code> folder. The PKG file is more of a typical installer as on Windows.<\/p>\n

    Of course, the problem with anything MacOS is that Apple really doesn\u2019t want you to do anything with MacOS if you\u2019re not running MacOS already. This can be worked around<\/a>, but just getting to the point of compiling for MacOS without running XCode on MacOS on real Apple hardware is a bit of a fool\u2019s errand. Not to mention Apple\u2019s insistence on signing these packages, if you don\u2019t want the end-user to have to jump through hoops.<\/p>\n

    Although I have built both iOS and OS X\/MacOS applications in the past \u2013 mostly for commercial projects \u2013 I decided to not bother with compiling or testing my projects like NymphCast for Apple platforms without easy access to an Apple system. Of course, something like Homebrew<\/a> can be a viable alternative to the One True Apple Way\"\u2122\" if you merely want to get OSS o MacOS. I did add basic support for Homebrew in NymphCast, but without a MacOS system to test it on, who knows whether it works.<\/p>\n

    Anything But Linux<\/h2>\n

    The world of desktop systems is larger than just Windows, MacOS and Linux, of course. Even mobile OSes like iOS and Android can be considered to be \u2018desktop OSes\u2019 with the way that they\u2019re being used these days, also since many smartphones and tablets can be hooked up to to a larger display, keyboard and mouse.<\/p>\n

    How to bootstrap Android<\/a> development, and how to develop native Android<\/a> applications has been covered before, including putting APK files together. These are the typical Android installation files, akin to other package manager packages. Of course, if you wish to publish to something like the Google Play Store, you\u2019ll be forced into using app bundles, as well as various ways to signing the resulting package.<\/p>\n

    The idea of using a package for a built-in package manager instead of an executable installer is a common one on many platforms, with iOS and kin being similar. On FreeBSD, which also got a NymphCast port, you\u2019d create a bundle for the pkg<\/code> package manager, although you can also whip up an installer. In the case of NymphCast there is a \u2018universal installer\u2019 built into the Makefile<\/a> after compilation via the fully automated setup.sh<\/code> shell script, using the fact that OSes like Linux, FreeBSD and even Haiku are quite similar on a folder level.<\/p>\n

    That said, the Haiku port of NymphCast is still as much of a Beta as Haiku itself, as detailed in the write-up<\/a> which I did on the topic. Once Haiku is advanced enough I\u2019ll be creating packages for its pkgman<\/code> package manager as well.<\/p>\n

    The Linux Chaos Vortex<\/h2>\n

    \"\"<\/a>There is a simple, universal way to distribute software across Linux distributions, and it\u2019s called the \u2018tar.gz method\u2019, referring to the time-honored method of distributing source as a tarball, for local compilation. If this is not what you want, then there is the universal RPM installation format which died along with the Linux Standard Base<\/a>. Fortunately many people in the Linux ecosystem have worked tirelessly to create new standards which will definitely, absolutely, totally resolve<\/a> the annoying issue of having to package your applications into RPMs, DEBs, Snaps, Flatpaks, ZSTs, TBZ2s, DNFs, YUMs, and other easily remembered standards.<\/p>\n

    It is this complete and utter chaos with Linux distros which has made me not even try to create packages for these, and instead offer only the universal .tar.gz<\/code> installation method. After un-tar-ing the server code, simply run setup.sh<\/a><\/code> and lean back while it compiles the thing. After that, run install_linux.sh<\/code> and presto, the whole shebang is installed without further ado. I also provided an uninstall_linux.sh<\/code> script to complete the experience.<\/p>\n

    That said, at least one Linux distro has picked up NymphCast and its dependencies like Libnymphcast and NymphRPC into their repository: Alpine Linux.<\/a> Incidentally FreeBSD also has an up to date package<\/a> of NymphCast in its repository. I\u2019m much obliged to these maintainers for providing this service.<\/p>\n

    Perhaps the lesson here is that if you want to get your neatly compiled and packaged application on all Linux distributions, you just need to make it popular enough that people want to use it, so that it ends up getting picked up by package repository contributors?<\/p>\n

    Wrapping Up<\/h2>\n

    With so many details to cover, there\u2019s also the easily forgotten topic that was so prevalent in the Windows installer section: integration with the desktop environment. On Windows, the Start menu is populated via simple shortcut files, while one sort-of standard on Linux (and FreeBSD as corollary) are Freedesktop\u2019s<\/a> XDC Desktop Entry<\/a> files. Or .desktop<\/code> files for short, which purportedly should give you a similar effect.<\/p>\n

    Only that\u2019s not how anything works with the Linux ecosystem, as every single desktop environment has its own ideas on how these files should be interpreted, where they should be located, or whether to ignore them completely. My own experiences there are that relying on them for more advanced features, such as auto-starting a graphical application on boot (which cannot be done with Systemd, natch) without something throwing an XDG error or not finding a display is basically a fool\u2019s errand. Perhaps that things are better here if you use KDE Plasma as DE, but this was an installer thing that I failed to solve after months of trial and error.<\/p>\n

    Long story short, OSes like Windows are pretty darn easy to install applications on, MacOS is okay as long as you have bought into the Apple ecosystem and don\u2019t mind hanging out there, while FreeBSD is pretty simple until it touches the Linux chaos via X11 and graphical desktops. Meanwhile I\u2019d strongly advise to only distribute software on Linux as a tarball, for your sanity\u2019s sake.<\/p>\n

    Blog \u2013 Hackaday Read More<\/a><\/p>\n

    \u200b<\/p>","protected":false},"excerpt":{"rendered":"

    After you have written the code for some awesome application, you of course want other…<\/p>\n","protected":false},"author":5,"featured_media":14636,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"twitter_16139062_16139062":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[176,109],"tags":[5289,110,115,1438,1500],"class_list":["post-37987","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-computers","category-hackaday","tag-freebsd","tag-hackaday","tag-linux","tag-macos","tag-windows"],"_links":{"self":[{"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/posts\/37987","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/comments?post=37987"}],"version-history":[{"count":1,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/posts\/37987\/revisions"}],"predecessor-version":[{"id":38092,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/posts\/37987\/revisions\/38092"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/media\/14636"}],"wp:attachment":[{"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/media?parent=37987"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/categories?post=37987"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/twiar.net\/wp-json\/wp\/v2\/tags?post=37987"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}