Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: How to make installer for my game?  (Read 1309 times)

0 Members and 1 Guest are viewing this topic.


  • Jr. Member
  • **
  • Posts: 56
    • View Profile
How to make installer for my game?
« on: May 29, 2017, 09:16:44 pm »
How can I make an installer that will install all my game files and install latest VC++ redistributables? And what about OpenAL and it's license? Thanks :).


  • SFML Team
  • Hero Member
  • *****
  • Posts: 10914
    • View Profile
    • development blog
    • Email
Re: How to make installer for my game?
« Reply #1 on: May 29, 2017, 10:01:03 pm »
This is not really a question related to SFML and thus you probably won't receive as quick or as good of an answer as you'd get on sites like StackOverflow.

Also, how much time have you spent investigating this topic? I'm certain that a few smart queries on Google will yield lots of useful results already. ;)

OpenAL is LGPL licensed and thus you'll need to ship the DLL with your executable.
For really detailed information you'd have to talk to a lawyer.
Official FAQ: https://www.sfml-dev.org/faq.php
Official Discord Server: https://discord.gg/nr4X7Fh
Dev Blog: https://duerrenberger.dev/blog/


  • Hero Member
  • *****
  • Posts: 1848
  • Back to C++ gamedev with SFML in May 2023
    • View Profile
    • Email
Re: How to make installer for my game?
« Reply #2 on: May 30, 2017, 01:47:52 am »
You could ship the MS dlls near your exe, I'm not sure if it's legal though.
As for installer: you can try NSIS, some commercial solution or making your own (in Qt, LCL, GTK+, FLTK, etc. probably not recommended unless you want to have the bragging rights and extra fun).
I personally prefer simple 100% self contained zip files (not even these self extracting ones, 100% plain zip files) but an installer can have some advantages I guess (installing dependencies, setting stuff up, finding user home dir to save stuff and configs to, etc).

As for OpenAL and other LGPL stuff, the agreed upon way seems to be: use a dll and say in a README or somewhere that you use LGPL licensed lib named so and so. https://softwareengineering.stackexchange.com/a/86158

In theory a source code link, copy or a point of contact to request a copy is required* and full license text should be included but.. many people skip that and the authors don't seem to ever care. Due to problems with GPL, LGPL, etc. people seem to follow them in the spirit only, unless someone does something really crazy and even then the first action is a polite reminder, not instant fucktillion dollars lawsuit/DMCA equivalent/whatever since that'd be a huge gift to enemies of FOSS and an image suicide for the authors of the library and the library itself.

* Or something like that. There are tons of edge cases and people online, interpretations of the license text, opinions of library authors, FAQs on FSF and so on all seem to argue and disagree what is required exactly.
« Last Edit: May 30, 2017, 03:03:32 am by FRex »
Back to C++ gamedev with SFML in May 2023