As usual while waiting for the next release - don't forget to check the nightly builds in the forum.
copystrings.cpp:10:17 error: calling fdopen: Bad file descriptor
#include "sdk.h"
although it should not have anything to do with it : try <sdk.h> ??
comment out the ifdef CB_PRECOMP, sdk.h the else and endif, just to see if copystrings compiles.
Woops : other problems,I have error in the building of codestat : Seems Zlika's commit does not work on linux.codestatconfig.cpp -> will fix them once I am back in windows.
------- Build: default in Code statitstics (Unix) -------
very weird. I could build on linux, except from the codestats problem. Are you on rev 2216 on linux ?? Since rev 2216 was the change to codestats.
so it seems sdk.h is still correct (relief ...), why can it be used in the other plug-ins and not in copystrings By the way, copystrings did not compile on my system, meaning it is NOT included in the build system.I use command line : make --> and indeed ther's no makefile in the copystrings, so it is left out. How did you build it ?? Are the settings for the copystrings project ok then
totally different things seem to happen with : 1) make build 2) cbp buildI think I recall something that the pch are not interchangeable between 1) and 2). But there seem to be more differences, since we both have same compiler (and version of compiler), my make build couldn't compile the codestat, and your without a problem.
--> that will be the next revision, and the nightly build will be based on that one.
commited
could you try with out the updates (or uncomment the lines in copystrings.cpp) and remove the following line from your copystring-unix.cbp : <Add option='-include "sdk.h"' />
Quote from: killerbot on March 19, 2006, 11:43:03 pmcould you try with out the updates (or uncomment the lines in copystrings.cpp) and remove the following line from your copystring-unix.cbp : <Add option='-include "sdk.h"' />Ok. I finish to build C::B and .deb package and I will give it a try .Best wishes,Michael
any news on this ??
Process file as if #include "file" appeared as the first line of the primary source file. However, the first directory searched for file is the preprocessor's working directory instead of the directory containing the main source file. If not found there, it is searched for in the remainder of the #include "..." search chain as normal.