Yes, I see now. The problem with this is that the options are stored inside configure, which is an executable(vs a script on linux).
I don't think there is a problem in creating a new version of the installer. Qt releases are not that often and I think it is normal to update the installer to handle the new qt version.
Maybe the options together with their descriptions should be stored in an external file, which should be updated with every qt release, while keeping the options for the older releases. This way the installer doesn't have to be rebuilt.
You can always run configure -help and inspect the options, so an external file is not that important. The problem is you have to think about handling those options afterwards The simplest solution is to just... ignore new switches or give a list of options to enable/modify them at the end of the configuration process and I think it's a good solution for a start.
Bookmarks