Code::Blocks Forums
Developer forums (C::B DEVELOPMENT STRICTLY!) => Development => Topic started by: ouch on June 13, 2011, 06:22:47 pm
-
I'm getting this error when compiling now:
.objs\src\main.o:C:\codeblocks\src\src\main.cpp|1072|undefined reference to `_imp__cbEVT_PLUGIN_LOADING_COMPLETE'|
I did a rebuild and it's still there.
win 7 64bit
tdm mingw
-
welcome to the domain of .pch problems.
If you can try a fresh checkout,and then build again.
-
welcome to the domain of .pch problems.
If you can try a fresh checkout,and then build again.
Before doing a fresh checkout, I suggest to remove include/*.gch manually.
If that does not help also remove devel and output and probably .objs folder.
-
If that does not help also remove devel and output
Yes, that might be the solution, manually deleting *.gch and .objs dir is not sufficient
-
Well tell you what, since I have an sample of the problem to work off of, I'll experiment with what actually breaks it and see if I can't create a batch/shell script to fix the issue so we don't have to keep starting from scratch.
I'm pretty busy today at work though. I wouldn't expect anything till a bit later in the week.
-
Deleting .objs and devel works here.
Recently, a few strings have been changed by introducing many \r escape sequences. But, poedit, when used to translate those strings, claims that these escape sequences should not be used in internationalized messages ! I think that those sequences have been introduced/modified by a Windows user, but are not necessary. Could someone delete them from sources ?
gd_on
-
Can you provide the exact revision where the change was made?
A patch would be even better :)
-
just deleting devel works here.
so lets see here...
We have the devel, obj directories and the 3 gch files in include. Is there anything else that might need to be nuked when something goes bad?
-
Can you provide the exact revision where the change was made?
A patch would be even better :)
I think the last \r escape sequences where introduced with rev 7209 in advanced_compiler_options.xrc.
More, each troubling \r I can find in the C::B code seems to be found in .xrc files. But those files, if I'm right, are automatically generated by a wxwidget code generator, so providing a patch, may be not very useful (and within those file, the \r is in fact coded by #x0D). It's the original code or configuration which needs to be modified, not only the resulting .xrc file.
gd_on