Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B
Built in support fro crosscompiling
MortenMacFly:
--- Quote from: ivucica on December 10, 2007, 04:52:25 pm ---It should, however, automatically detect MinGW. I ask nothing more ;)
--- End quote ---
How would you do that? Most users extract the compiler that is mostly shipped as tar.gz to any place on their HDD. Should C::B really search across all your (320GB) HDD's to find MinGW if you know where it is? Any maybe you have two version of GCC installed (as I do) - should C::B just guess which one to use? No thanks. We look at the default "installation" path which is C:\MinGW. If it's not there - the user has to configure it. Period.
With regards, Morten.
denk_mal:
--- Quote from: MortenMacFly on December 11, 2007, 02:38:01 pm ---
--- Quote from: ivucica on December 10, 2007, 04:52:25 pm ---It should, however, automatically detect MinGW. I ask nothing more ;)
--- End quote ---
How would you do that? Most users extract the compiler that is mostly shipped as tar.gz to any place on their HDD. Should C::B really search across all your (320GB) HDD's to find MinGW if you know where it is? Any maybe you have two version of GCC installed (as I do) - should C::B just guess which one to use? No thanks. We look at the default "installation" path which is C:\MinGW. If it's not there - the user has to configure it. Period.
With regards, Morten.
--- End quote ---
I totally agree with you, that the user has to configure it, if a quick search dosn't find MinGW cause searching the entire HDD is not an option but taking a look at the path enviroment variable (like whereis on linux) could be an option (also for Windows).
denk_mal
MortenMacFly:
--- Quote from: denk_mal on December 12, 2007, 09:06:48 am ---but taking a look at the path enviroment variable (like whereis on linux) could be an option (also for Windows).
--- End quote ---
This still does not solve the issue if you have more than one gcc compiler installed and (possible, too) you have another tool called gcc.exe for example. I promise: We would get the same amount of user requests saying MinGW was not detected or false detected due to that as we have now.
With regards, Morten.
Biplab:
--- Quote from: denk_mal on December 12, 2007, 09:06:48 am ---I totally agree with you, that the user has to configure it, if a quick search dosn't find MinGW cause searching the entire HDD is not an option but taking a look at the path enviroment variable (like whereis on linux) could be an option (also for Windows).
--- End quote ---
Definitely it's an option. But MinGW cross-compiler is not widely available in all distros. Also the available version is quite old and comes with GCC only.
I prefer to not to use /usr/local dir to compile and install the cross-tools. In two of my PCs they are in /usr/local/cross-tools dir and in /home/biplab/cross-tools dir. This is one such possible cases where C::B will fail to detect it even with a whereis patch (unless one adds it to PATH).
Trust me, only couple of clicks are necessary to get it working with C::B. I believe that is not too difficult. :)
darthdespotism:
--- Quote from: Biplab on December 12, 2007, 04:57:19 pm ---
Definitely it's an option. But MinGW cross-compiler is not widely available in all distros. Also the available version is quite old and comes with GCC only.
--- End quote ---
Which distros do you mean by this? Ubuntu 7.04 had IMO the latest release of MinGW and my Lenny offers the 4.2-sjlj TechPreview. Both with g++
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version