Am Samstag, 6. Oktober 2012, 16:53:13 schrieb Andrew Pennebaker: > The Windows gforth installer > executable<http://www.complang.tuwien.ac.at/forth/gforth/>works fine, > except for the fact that it requires the user to manually add > the gforth binaries to the PATH environment variable. Could future versions > of the installer do this automatically?
Yes, this is possibly, at least under NT-based Windows, where the PATH variable is in the registry. > I'm cloning the flat files and working on an MSI that would do this, > using Advanced > Installer <http://www.advancedinstaller.com/>. I've done the same thing for > about 30 other command line programs, but for some reason the gforth > MSI<https://github.com/mcandre/gforth-win> that > Advanced Installer produces is giving me strange errors. Advanced Installer might be a good tool, but as we are an official GNU project, we are going to use free software as tools when available. Free as in Free Open Source, not as in "no cost". And Inno Setup is actually a quite good tool, though it doesn't create a .msi file. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://bernd-paysan.de/
signature.asc
Description: This is a digitally signed message part.
