User forums > Help
why lock when it IS related to codeblocks?? check other post
stahta01:
You have to setup the directory search correctly when using Boost.
Edit: I guessed, It was an directory search Configuration issue; but, was wrong.
Tim S
Under search directories -> compiler I have
C:\Apps\MinGW_Boost\boost_1_38_0
C:\Apps\MinGW_Boost\include
You have to include the boost directory before the normal Mingw include.
Tim S
techwar:
no. what the problem was is c::b was looking for the wrong filenames for the mingw programs when told it was to use the minGW compiler
Jenna:
--- Quote from: techwar on May 30, 2009, 03:24:43 am ---no. what the problem was is c::b was looking for the wrong filenames for the mingw programs when told it was to use the minGW compiler
--- End quote ---
So it was in fact a configuration error and not a C::B related problem.
C::B can not know the names of each and every MinGW-compiler versions that exist.
No excusion from me for locking your other topic !
techwar:
And THAT'S why C::B will suck and die, because of you people being assholes.
C::B autodetecting MinGW and inserting the wrong thing in the compiler, etc... fields IS a C::B issue.
It's NOT that hard to fix it. If you don't want it to be a C::B issue, then take the AUTO-DETECT feature OUT.
AND I state again... Forthe HELP section of a product's forum, you suck and this will be the reason Code::Blocks dies. Poor customer service kills innumerable businesses and/or projects every time.
Good luck, you're going to need it. (and a definite change of attitude toward your users)
Jenna:
--- Quote from: techwar on May 30, 2009, 07:05:41 pm ---And THAT'S why C::B will suck and die, because of you people being assholes.
C::B autodetecting MinGW and inserting the wrong thing in the compiler, etc... fields IS a C::B issue.
It's NOT that hard to fix it. If you don't want it to be a C::B issue, then take the AUTO-DETECT feature OUT.
AND I state again... Forthe HELP section of a product's forum, you suck and this will be the reason Code::Blocks dies. Poor customer service kills innumerable businesses and/or projects every time.
Good luck, you're going to need it. (and a definite change of attitude toward your users)
--- End quote ---
first:
why are you not willing to share your solution ?
What did C::B use as executable, and what is the correct name you need ?
and second:
Do you know the difference between a compiler directory and the compiler itself ?
In the attached picture you can see clearly, that C::B (tries) to autdetect the compilers directory.
But as you know (that was your problem, if I understood correctly, you never told us exactly what went wrong, why ??) there might be several compiler executables inside the same directory (g++.exe, mingw32-g++.exe, mingw32-g++-4.2.1.exe, mingw32-g++-dw2.exe ...), so C::B takes the standard names, and that will work in most cases.
That's the cause why there is the hint below the text-box:
--- Quote ---NOTE: All programs below, must exist either in the "bin" sub-directory of this path or in any of the "Additional paths" ...
--- End quote ---
You have to read carefully and think yourself, but that is something many people seem to have unlearned.
I'm sorry for you !
[attachment deleted by admin]
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version