odd compiler behavior when compiling CB

[sethjackson]

I just noticed something that might be the cause of a lot of my problems.  In the Build Options, directories tab, compilers tab of the code::block project is this directory:

$(#WX)\contrib\include

What is used from the contrib directory?  I don't have this in my wx libraries directory.  It is in my sandbox.  What is used from it, and do I need to compile anything from it before compiling CB?

jmccay

Well C::B used to use STC which was in contrib..... I don't think anything uses it now.......

[jmccay]

Well C::B used to use STC which was in contrib..... I don't think anything uses it now.......

It's in the project to be built, and the contrib directory is referenced.  Also, It is where I am getting my errors.

jmccay

[sethjackson]

Well C::B used to use STC which was in contrib..... I don't think anything uses it now.......

It's in the project to be built, and the contrib directory is referenced.  Also, It is where I am getting my errors.

jmccay

Hmm what is referencing it?

[thomas]

Nothing is referencing it, and it shouldn't cause a problem. I always deleted the contrib folder after building wxWidgets, and it does not do anything.
The reason why it is still there is because in wxWidgets 2.6.2 and earlier, STC and XRC are found there, so it wouldn't otherwise be possible to build with those versions.

[jmccay]

Nothing is referencing it, and it shouldn't cause a problem. I always deleted the contrib folder after building wxWidgets, and it does not do anything.
The reason why it is still there is because in wxWidgets 2.6.2 and earlier, STC and XRC are found there, so it wouldn't otherwise be possible to build with those versions.

What happened with 2.6.3?  STC still seems to be located under contrib.  Do I have to build it seperately?

jmccay

[thomas]

STC still seems to be located under contrib.  Do I have to build it seperately?

Yes, no.
Yes, it is still located there, no, we don't use it any more.
XRC is no longer in contrib (we do use that), so as I said, we don't need that path in 2.6.3 any more.

[jmccay]

Ok.  Thank you.

[jmccay]

I was just browsing/searching over at mingw users list, and it seems a patch (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20345) has been applied to fix the warnings, but I am still trying to find out more information.  The messages I found were from late 6/2006.  Hopefully, this will fix the warning problem, and I can get my hands on a copy of mingw using it.

jmccay

[jmccay]

I was just browsing/searching over at mingw users list, and it seems a patch (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20345) has been applied to fix the warnings, but I am still trying to find out more information.  The messages I found were from late 6/2006.  Hopefully, this will fix the warning problem, and I can get my hands on a copy of mingw using it.

jmccay

   I was just told that the patch was applied to the gcc 4.2 branch, and unfortunately, I was also told that the mingw/cygwin versions are far from stable.  So, it looks like I am going to have to turn off warnings for now.

jmccay