User forums > Nightly builds
The 12 september 2010 build (6583) CODECOMPLETION BRANCH version is out.
ollydbg:
--- Quote from: ironhead on September 14, 2010, 04:08:01 am ---It seems to be related to the mingw-w64 tool chain. If I set the compiler to the 'mingw.org' tool chain, everything works as expected. Is there a way to check to see what the parser doesn't like about the mingw-w64 headers?
Incidentally, there seems to be a bug in that the default compiler headers are parsed irregardless of what the compiler is set to in the project.
--- End quote ---
The simple logic when CC get all the compiler headers directory is:
1. CC will run a dummy preprocessor command "cpp -v -E -x c++ nul"
2. Then CC will read the output of this command and parse (If I remember correct, it use regex match) this file and correct all the directories as it's search path.
To your problem, it seems: the directories were not correctly parsed by CC, so you need to add them manually.
I don't have a Win64 system, But I think it is easy to fix. :D
Loaden:
Improve V2:
Change Log
1. Make system header files code-completion configurable
2. Enhance performance by CC member variables
3. Fixed switch parser error
4. Add some debug log
Loaden:
--- Quote from: ollydbg on September 15, 2010, 02:40:57 am ---
--- Quote from: ironhead on September 14, 2010, 04:08:01 am ---It seems to be related to the mingw-w64 tool chain. If I set the compiler to the 'mingw.org' tool chain, everything works as expected. Is there a way to check to see what the parser doesn't like about the mingw-w64 headers?
Incidentally, there seems to be a bug in that the default compiler headers are parsed irregardless of what the compiler is set to in the project.
--- End quote ---
The simple logic when CC get all the compiler headers directory is:
1. CC will run a dummy preprocessor command "cpp -v -E -x c++ nul"
2. Then CC will read the output of this command and parse (If I remember correct, it use regex match) this file and correct all the directories as it's search path.
To your problem, it seems: the directories were not correctly parsed by CC, so you need to add them manually.
I don't have a Win64 system, But I think it is easy to fix. :D
--- End quote ---
I don't have a x64 system too.
So, I need you debug log, see post in here.
http://forums.codeblocks.org/index.php/topic,13291.msg89450.html#msg89450
Loaden:
--- Quote from: killerbot on September 14, 2010, 10:26:17 am ---I have a strange issue. I have a very little test example using boost::variant.
[on linux]
That means main.cpp does :
--- Code: ---#include <boost/variant.hpp>
--- End code ---
I right click on it to open that header. ==> Not found : boost/variant.hpp
Right click again and choose to open it --> now it succeeds.
I noticed it also happened with regular std header files.
Anyone else suffering from this ??
--- End quote ---
I think it will be fixing in this post.
http://forums.codeblocks.org/index.php/topic,13291.msg89512.html#msg89512
ironhead:
--- Quote from: Loaden on September 15, 2010, 07:33:39 am ---
--- Quote from: ollydbg on September 15, 2010, 02:40:57 am ---
--- Quote from: ironhead on September 14, 2010, 04:08:01 am ---It seems to be related to the mingw-w64 tool chain. If I set the compiler to the 'mingw.org' tool chain, everything works as expected. Is there a way to check to see what the parser doesn't like about the mingw-w64 headers?
Incidentally, there seems to be a bug in that the default compiler headers are parsed irregardless of what the compiler is set to in the project.
--- End quote ---
The simple logic when CC get all the compiler headers directory is:
1. CC will run a dummy preprocessor command "cpp -v -E -x c++ nul"
2. Then CC will read the output of this command and parse (If I remember correct, it use regex match) this file and correct all the directories as it's search path.
To your problem, it seems: the directories were not correctly parsed by CC, so you need to add them manually.
I don't have a Win64 system, But I think it is easy to fix. :D
--- End quote ---
I don't have a x64 system too.
So, I need you debug log, see post in here.
http://forums.codeblocks.org/index.php/topic,13291.msg89450.html#msg89450
--- End quote ---
I've been away from home for the past couple of days (and away from my x64 machine). I'll be home tonight and I'll run the build you provided and send you the logs.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version