Hello!
The installer of the latest 8.02 release is a NSIS one, are the installer scripts available anywhere (I'm not able to find them in svn)? I would have the idea of a patch (or at least a 'feature suggestion'), that during installation one is able to choose the path where MinGW gets installed.
Thanks,
Oliver
Quote from: olipfei on March 19, 2008, 01:28:20 PM
that during installation one is able to choose the path where MinGW gets installed.
The latest NSIS script has Lieven. He promised to upload anytime soon to SVN but I guess he is just too busy.
As for your suggestion: We have a reason why MinGW is just a sub-folder of C::B and won't change it in the installer.
The reason is plain simple: The compiler plugin can detect MinGW there and in a *very few* other places automatically, so C::B is properly configured after tinstallation. This mechanism won't work if you install MinGW "anywhere". So such a patch would be rejected. Sorry.
I understand; but I had some problems with the default directory of MinGW under Windows Vista. I was unable to compile wxWidgets with the makefile: make was unable to find some executables, even if they were in the system path. I resolved the problem moving MinGW in c:\mingw.
Quote from: MortenMacFly on March 19, 2008, 03:52:50 PM
The latest NSIS script has Lieven. He promised to upload anytime soon to SVN but I guess he is just too busy.
Is the NSIS installer script still not available? The CodeBlocks 8.02 source archive has a Inno Setup script but the release uses NSIS.
I am trying to automate the setup of a customized default.conf with additional compilers and also CodeBlocks settings different from the defaults. Possibly there is a simple way of doing this without changing the installer? It would be simpler if a base default.conf was in the CodeBlocks binary directory and the one in %APPDATA%/home only stored changes from the base file, particularly on PCs that have multiple users defined.
Hmm, I was under the impression I have added them in the meantime. Will check.
EDIT : it's there, not in trunk but in setup
Quote from: killerbot on August 09, 2008, 10:39:35 AM
it's there, not in trunk but in setup
Thanks for pointing this out. Before I was looking in trunk/src/setup instead of setup.