User forums > Help
CodeBlocks and Compiler
prr:
--- Quote from: fvbommel ---I installed MinGW in a non-default location and C:\WINNT\MinGW.ini contains the correct path, so it's not on every non-default install. I'm running Windows 2000 though, maybe that makes a difference...
--- End quote ---
2nd try:
I have uninstalled mingw and _manually_ deleted %windir%\mingw.ini, than reinstalled mingw, and the ini and it's expected contents was there.
After this, I have uninstalled mingw a second time but _without_ manually delete the ini file and I've observed that the mingw uninstaller instead of deleting ini file, _empy_ it! Producing the aforesaid 0 byte lenght ini file, that will not be overwritten or updated by a new fresh installation.
walter
bszente:
This means that you cannot trust in MinGW.ini contents. It seems that the only almost certain solution is to search for one of the mingw32-....exe files.
mandrav:
I will try to contact the MinGW team. Meanwhile I 'm not investing time in this because the next release will probably come with MinGW included, as an option.
Yiannis.
rickg22:
I HAVE A SOLUTION!
It's simple.
1) Get the Windows env. variable 'PATH'. For each of the directories found, search it for any mingw ocurrences. (like make sure it has the folders BIN and MINGW/BIN).
2) If still you don't find it, then "bail out" and just ask the user where he downloaded the file.
My reasoning? Simple. If one has manually moved the MINGW installation, the he probably set up the path manually, too! :D
mandrav:
IIRC, the MinGW setup does not update the PATH env var...
Or does it? Can someone confirm this?
Yiannis.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version