User forums > General (but related to Code::Blocks)

error compiling nightly build revision 5046

<< < (2/3) > >>

MortenMacFly:

--- Quote from: stahta01 on May 11, 2008, 07:06:14 am ---I am Guessing that it is another NON PCH build issue.

--- End quote ---
You are guessing right. Hopefully you can provide a patch... (as usual... ;-). One thing I figured out myself - but this lib_finder stuff...?!

Jenna:
I just compiled C::B svn5046 with "--enable-pch=no" and got the first error in "global.cpp", but after adding "projectmanager.h" everything compiled fine (including all contrib-plugins).
debian sid/experimental
64-bit
gcc 4.2.3
wxWidgets 2.8.7

r.stiltskin:
I realized that I had inadvertently used an old compiler (gcc 3.3, which I had to use for another project).  After switching back to gcc 4.1 everything compiled, including all contrib-plugins, but when I  start code::blocks, libfinder does not load (message pops up about being built for a different version of codeblocks).

What is this non-pch issue?

MortenMacFly:

--- Quote from: r.stiltskin on May 11, 2008, 03:24:08 pm ---(message pops up about being built for a different version of codeblocks).

--- End quote ---
You should really do  a clean and re-build when you have messed around with different compiler versions (especially if the major number changes). This will most likely also resolve this conflict.


--- Quote from: r.stiltskin on May 11, 2008, 03:24:08 pm ---What is this non-pch issue?

--- End quote ---
We take advantage of pre-compiled header files within C::B. This improves compiling speed a lot but also often causes some laziness concerning includes. The result is a broken build with compiler not supporting PCH (like GCC 3.3) and/or if you disable PCH explicitly using "--enable-pch=no".

Search google for more info on PCH if that doesn't ring a bell.

r.stiltskin:
I did "make clean" before I compiled with gcc4.1.  Shouldn't that have taken care of these issues?

Edit: I just went into the lib_finder directory & ran "make clean" and "make" there, then re-linked everything with "make install" in the trunk directory and now libfinder does load.

I'm not very good at reading makefiles.  Does "make clean" in the top makefile not delete all the object files in the plugins directories?

Navigation

[0] Message Index

[#] Next page

[*] Previous page