kdatrainer.blogg.se

I suspect I have some problem with default include paths, but maybe not. Since I am trying to compile with the same GCC compiler and toolset on both OS with CodeBlocks, all the compiler switches remain the same as CodeBlocks on Linux. Perhaps the best way to say that is, the code compiles and runs in VisualStudio2005pro *and* CodeBlocks on Linux at this point, the only difference being LINUX is defined (in the IDE) on Linux, and WINDOZE is defined (in the IDE) on Windoze (in both VisualStudio2005 and CodeBlocks). What I mean is, my code contains #ifdef LINUX and #ifdef WINDOZE around any and all code (and #includes) that cannot be identical on both OS - and does *not* in any way expect or depend upon emulating linux on windoze, or emulating windoze on linux.

Here are the facts that seem most relevant, and my current symptom.įirst, understand that *this* portable application is not portable in the same way as many others (ala cygwin, I suspect). Sorry to bother you again, but I'm going in circles. Unfortunately, now I have problems compiling the code with CodeBlocks on Windoze. With some help from this forum, I can now compile, execute, debug my engine with CodeBlocks on Linux.

I am developing a cross-platform 3D game/graphics/simulation engine and am trying to switch from my old IDEs to CodeBlocks.