User forums > Help

Improving compiler autodetection (was: Re: registry)

<< < (2/2)

Michael:

--- Quote from: rickg22 on November 29, 2005, 07:35:54 pm ---yeah but we'd have to know which directories (or files?) are specific for other compilers.

--- End quote ---
Yes, you're right. But we can always ask the user where she/he has installed the compiler and then automatically detect what it is needed (eventually, by asking user's confirmation).

Best wishes,
Michael

MortenMacFly:

--- Quote from: rickg22 on November 29, 2005, 06:31:20 pm ---I'm thinking of an algorithm: [...]

--- End quote ---
That reminds me of those silly installers that first do a folder search on all HDD's on a system. That's something I personally hate because I have thousands of folders and this usually leads to a very big delay in time which I could perfectly use to point to the application/folder the installer it is looking for... :?

...just my personal thoughts.

Morten.

takeshimiya:
True, the algorithm must search for most common places (ie. mingw's registry installer, C:\mingw, C:\dev-cpp\mingw, D:\mingw, C:\Devel\mingw, ...).
If nothing found, then a question "Do you want to search on all disks for the compiler?" pops to the user.

rickg22:
Yeah well the problem is that when specifying the compiler on the first run, you can't (IIRC) specify the directory. There's only the "autodetect" button.

Navigation

[0] Message Index

[*] Previous page