User forums > Using Code::Blocks
help with code complete, MSVS and a minor bug I've found
neil:
Thanks, this new version is much, much nicer :)
However, I still don't get any help when typing 'object->' and I still get the same error with VS2003.
I don't know if I'm doing something wrong or whether it is meant to be like this, but when I switch compilers (between GCC and MSVC), it gets some of it's compiler/linker flags mixed up. For example, after minGW compiled ok, I switched to MSVC, enabled /MD flag, then when I switched back to minGW and tried to compile it failed saying '/MD no such file'. Even after removing the flag from MSVC, minGW gives me the same error and I can't compile minGW now.
While I'm here, I guess you could call this a feature request (unless it' been done), but when you switch compilers, it would be nice to get a completely new set of values in the build options, e.g. in minGW I reference a few .a files but when I switch to MSVC these are still there, similarly for MSVC, minGW settings shows a few .lib files.
Thanks.
killerbot:
--- Quote from: neil on February 24, 2006, 03:21:46 pm ---Thanks, this new version is much, much nicer :)
However, I still don't get any help when typing 'object->' and I still get the same error with VS2003.
I don't know if I'm doing something wrong or whether it is meant to be like this, but when I switch compilers (between GCC and MSVC), it gets some of it's compiler/linker flags mixed up. For example, after minGW compiled ok, I switched to MSVC, enabled /MD flag, then when I switched back to minGW and tried to compile it failed saying '/MD no such file'. Even after removing the flag from MSVC, minGW gives me the same error and I can't compile minGW now.
While I'm here, I guess you could call this a feature request (unless it' been done), but when you switch compilers, it would be nice to get a completely new set of values in the build options, e.g. in minGW I reference a few .a files but when I switch to MSVC these are still there, similarly for MSVC, minGW settings shows a few .lib files.
Thanks.
--- End quote ---
Those compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.
mandrav:
--- Quote ---Those compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.
--- End quote ---
They don't interfere. If you change the compiler of a target, then any compiler specific options don't get converted for the new compiler.
This is not a bug. It is known limitation which will be fixed with the next compiler framework.
And before neil asks when will that be, it 'll be When It's Ready(tm).
neil:
Cheers, is there anyway I can get rid of this hidden '/MD' flag stopping mingw from compiling, other than creating a new project? As I mentioned, removing it from MSVC doesn't work. So they must interfere, otherwise MinGW wouldn't have picked it up. I guess it's an easy enough bug for anyone to recreate.
any thoughts on why MSVC compiler is trying to use the profiled dll?
Keep up the good work, it's appreciated :)
MortenMacFly:
--- Quote from: mandrav on February 24, 2006, 03:35:51 pm ---
--- Quote ---Those compiler switches should not interfere with each other, so if that's the case, you have discovered a bug.
--- End quote ---
They don't interfere.
--- End quote ---
mandrav: I'm afraid neil is right - I can reproduce this issue. I've created a simple C++ console project, compiled with GCC, it's fine. Then in the "Build options" I changed the compiler to "MSVCToolkit" and enabled the /MD switch. C::B complained: "You have changed the compiler used for the project. Do you want to use the same compiler for all the project's build targets too?" and I said "Yes". I couldnt' compile (rebuild), but anyway. Then I switched back to GCC and tried to compile (rebuild) again. And look at the log:
--- Code: ----------------- Build: default in Huhu ---------------
mingw32-g++.exe /MD -IE:\Devel\CodeBlocks\include -c main.cpp -o .objs\main.o
mingw32-g++.exe: /MD: No such file or directory
Process terminated with status 1 (0 minutes, 1 seconds)
0 errors, 0 warnings
--- End code ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version