Code::Blocks Forums
User forums => General (but related to Code::Blocks) => Topic started by: jvpic on July 13, 2006, 03:10:44 pm
-
Hi,
I'm new in C::B. I have compiled de wxWidgets with ming32 the default compiler of C::B. The dll is well constructed.
Console project compile very well.
I want to compile the template for GUI wxWidgets but C::B returns an error:
C::B don't find <wx/wxprec.h>
Somebody can help me ? :(
Thank you.
-
Another problem because <wx/wx.h> is not find !
The directories of install are :
c:\lang\CodeBlocks
et
c:\Lang\wxWidgets-2.6.3
-
Another problem because <wx.wx.h> is not find !
The directories of install are :
c:\lang\CodeBlocks
et
c:\Lang\wxWidgets-2.6.3
Don't you mean <wx.h>?
-
No I mean exactly <wx/wx.h> and <wx/wxprec.h>
These include files are referenced in the include files of the template !
-
No I mean exactly <wx/wx.h> and <wx/wxprec.h>
These include files are referenced in the include files of the template !
Really "/" not "\" ?
If "/" is the directory seperator then it should be a typo (Linux and *nix use this seperator, but not Windows).
Change it to <wx\wx.h> and <wx\wxprec.h>
Correct me if I'm wrong, but I don't think that mingw uses Linux paths on Win, or does it ?
-
Really "/" not "\" ?
If "/" is the directory seperator then it should be a typo (Linux and *nix use this seperator, but not Windows).
Change it to <wx\wx.h> and <wx\wxprec.h>
Correct me if I'm wrong, but I don't think that mingw uses Linux paths on Win, or does it ?
Yes it does. The directory separators in header files for wxWidgets on MSW are really "/". So it is in Dev-cpp and wxWidgets and also in URL !
-
Really "/" not "\" ?
If "/" is the directory seperator then it should be a typo (Linux and *nix use this seperator, but not Windows).
Change it to <wx\wx.h> and <wx\wxprec.h>
Correct me if I'm wrong, but I don't think that mingw uses Linux paths on Win, or does it ?
Yes it does. The directory separators in header files for wxWidgets on MSW are really "/". So it is in Dev-cpp and wxWidgets and also in URL !
Ok, then I'm wrong. Ignore it :lol:
-
add the wx base dir to your include paths, that's the dir that contains on your pc the subdir wx, which in turn contains wx.h.
Example : E:\data\killerbot\wxWidgets-2.6.3\include\
-
No I mean exactly <wx/wx.h> and <wx/wxprec.h>
These include files are referenced in the include files of the template !
I meant <wx/wx.h>. :oops:
You did have <wx.wx.h>.
Sorry my bad. :P
-
add the wx base dir to your include paths, that's the dir that contains on your pc the subdir wx, which in turn contains wx.h.
Example : E:\data\killerbot\wxWidgets-2.6.3\include\
Ok ! Killerbot, it compiles, hence I have a problem of dll : wxmsw26_gcc_custom.dll which was deplaced. But now all is in order. . I would think it myself !
Thank you. :P
The wxWidgets compilation is relatively a long process and is poorly documented. I have taken the option MONOLITHE=1 and of course the distribution must have the big dll. Perhaps could you indicate me a good and uptodate document for this !