From: Guenter <gue...@on...> - 2013-01-02 14:50:21
|
me, I am beginner. I installed Haskell platform, this package includes mingw, but unfornaturally without mingw32-make. So I installed the mingw-get-inst-20120426.exe and took c:\mingw\bin to the Path to install wxWidgets. With the wxFormBuilder I generated xxx.cpp and xxx.h files. If I try to compile xxx.cpp with g++ the xxx.h file will be found but not the incuded header files inside the xxx.h. It seems that the term "#include <wx/yyy.h>" will not interpreted by mingw. If I extended the path variable by \wx and modified the trem "#include <yyy.h>" then the header file yyy.h will be found. I have no idea to solve the problem best regards guenter |
From: Manolo <man...@gm...> - 2013-01-02 15:06:44
|
> me, I am beginner. > > I installed Haskell platform, this package includes mingw, but > unfornaturally without mingw32-make. So I installed the > mingw-get-inst-20120426.exe and took c:\mingw\bin to the Path to install > wxWidgets. With the wxFormBuilder I generated xxx.cpp and xxx.h files. > If I try to compile xxx.cpp with g++ the xxx.h file will be found but > not the incuded header files inside the xxx.h. It seems that the term > "#include <wx/yyy.h>" will not interpreted by mingw. Are you sure that a so extended app (like mingw) is not able to manage basic things as "#include"? Please, read the gcc/g++ docs. You can find the differences between <wx/xyz.h> and "wx/xyz.h". You can find the use of '-D' and '-L' parameters for g++. You would put your own files in a different folder than wx ones. |
From: Guenter <gue...@on...> - 2013-01-02 17:04:06
|
Am 02.01.2013 16:06, schrieb Manolo: >> me, I am beginner. >> >> I installed Haskell platform, this package includes mingw, but >> unfornaturally without mingw32-make. So I installed the >> mingw-get-inst-20120426.exe and took c:\mingw\bin to the Path to install >> wxWidgets. With the wxFormBuilder I generated xxx.cpp and xxx.h files. >> If I try to compile xxx.cpp with g++ the xxx.h file will be found but >> not the incuded header files inside the xxx.h. It seems that the term >> "#include <wx/yyy.h>" will not interpreted by mingw. > Are you sure that a so extended app (like mingw) is not able to manage > basic things as "#include"? > > Please, read the gcc/g++ docs. > You can find the differences between <wx/xyz.h> and "wx/xyz.h". > You can find the use of '-D' and '-L' parameters for g++. > You would put your own files in a different folder than wx ones. > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > Also: mailto:min...@li...?subject=unsubscribe This is what I got There are no docs with the mingw package, so I downloaded 770 side long GNU Compiler Collection. I did not find a solution for my problem. I never believed that mingw fails. I think I have to add something to g++, but I did find the right one. |
From: Manolo <man...@gm...> - 2013-01-02 17:37:24
|
First, read the link that Keith told in last post. Second, to use wxWidgets you must tell g++ where to find wxWidgets headers: at yourwxdir/include. Use '-I' or '-L' with g++ (see its doc, section 3.14 of gcc manual). Third, add also wx libs directory to the list of directories to be searched. If you compile a wx sample (e.g. ArtProvider) using in that sample dir: mingw32-make -f makefile.gcc (*) you'll see all needed parameters in the command line. (*) Well, depending of how your wx pack has been compiled, you need some more parameters (BUILD = release, etc.) |
From: Guenter <gue...@on...> - 2013-01-02 18:08:48
|
Am 02.01.2013 18:37, schrieb Manolo: > First, read the link that Keith told in last post. > > Second, to use wxWidgets you must tell g++ where to find wxWidgets > headers: at yourwxdir/include. Use '-I' or '-L' with g++ (see its doc, > section 3.14 of gcc manual). > > Third, add also wx libs directory to the list of directories to be searched. > > If you compile a wx sample (e.g. ArtProvider) using in that sample dir: > mingw32-make -f makefile.gcc (*) > you'll see all needed parameters in the command line. > (*) Well, depending of how your wx pack has been compiled, you need > some more parameters (BUILD = release, etc.) > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > Also: mailto:min...@li...?subject=unsubscribe After reading a bit more about gcc and include I believe that mingw take ´ wx/xxx.h ´ (out of #include <wx/xxx.h>) as a filename. How can I mingw explain that wx/ is a subdirectory of the include directory and xxx.h is the file name. All the system headers of wxWidgets are located in C:\wxWidgets\include\wx. C:\wxWidgets\include is the PATH variable. |
From: Paul M. <p.f...@gm...> - 2013-01-02 18:36:42
|
On 2 January 2013 18:08, Guenter <gue...@on...> wrote: > After reading a bit more about gcc and include I believe that mingw take > ´ wx/xxx.h ´ (out of #include <wx/xxx.h>) > as a filename. How can I mingw explain that wx/ is a subdirectory of the > include directory and xxx.h is the file name. > All the system headers of wxWidgets are located in C:\wxWidgets\include\wx. > C:\wxWidgets\include is the PATH variable. You don't want C:\wxWidgets\include in PATH. You need to use the -I argument to gcc, as so: gcc -I C:\wxWidgets\include ...rest of args... Paul |
From: Manolo <man...@gm...> - 2013-01-02 18:39:05
|
In order to include wx headers it's a good practice to write: #include "wx/file.h" instead of #include "file.h" where 'file.h' is the header needed. This way you can avoid using other headers with the same name (i.e. bitmap.h) but from another library. wx is organized in a way that many other .h files will also be automatically included from -in your case- 'C:\wxWidgets\include' So, you just need to add "-IC:\wxWidgets\include" to g++ command line and mingw will find 'wx/file.h' in that directory. The PATH variable is mainly used for executables (consider a .dll also as a executable file) not for headers. |
From: Guenter <gue...@on...> - 2013-01-03 10:16:41
|
Am 02.01.2013 19:38, schrieb Manolo: > In order to include wx headers it's a good practice to write: > #include "wx/file.h" > instead of > #include "file.h" > where 'file.h' is the header needed. This way you can avoid > using other headers with the same name (i.e. bitmap.h) but from > another library. > > wx is organized in a way that many other .h files will also be > automatically included from -in your case- 'C:\wxWidgets\include' > > So, you just need to add "-IC:\wxWidgets\include" to g++ command > line and mingw will find 'wx/file.h' in that directory. > > The PATH variable is mainly used for executables (consider a .dll > also as a executable file) not for headers. > > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > MinGW-users mailing list > Min...@li... > > This list observes the Etiquette found at > http://www.mingw.org/Mailing_Lists. > We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. > > _______________________________________________ > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > Also: mailto:min...@li...?subject=unsubscribe Thank you for understanding my problem and your help. With g++ -IC:\wxWidgets\include xxx.cpp it works without error message by the way, it seems to be commen sense that the PATH variable does not work for headers, but not for me. It was the first time I got this information. |
From: Gisle V. <gv...@br...> - 2013-01-02 20:15:06
|
"Guenter" <gue...@on...> wrote: > After reading a bit more about gcc and include I believe that mingw take > ´ wx/xxx.h ´ (out of #include <wx/xxx.h>) > as a filename. How can I mingw explain that wx/ is a subdirectory of the > include directory and xxx.h is the file name. > All the system headers of wxWidgets are located in C:\wxWidgets\include\wx. > C:\wxWidgets\include is the PATH variable. Simply put this in your environment (e.g. press WinKey-Break and enter Advanced | Environment). Or whatever method you use to setup your environment block. Add (or edit) this env-var: C_INCLUDE_PATH=c:/wxWidgets/include Thus when gcc looks for <wx/xxx.h> it will find a match in c:/wxWidgets/include/wx/xxx.h. (verify by gcc -v ...) But why wxWWidgets? Qt is so much better.. --gv |
From: Keith M. <kei...@us...> - 2013-01-02 21:00:30
|
On 02/01/13 20:14, Gisle Vanem wrote: > But why wxWWidgets? Qt is so much better.. In your opinion, maybe... That's tantamount to saying "why use emacs? vim is so much better". Please don't start such religious flame wars on this list. -- Regards, Keith. |
From: Keith M. <kei...@us...> - 2013-01-02 15:28:48
|
On 2 January 2013 14:50, Guenter wrote: > me, I am beginner. > > I installed Haskell platform, this package includes mingw, but > unfornaturally without mingw32-make. So I installed the > mingw-get-inst-20120426.exe and took c:\mingw\bin to the Path to install > wxWidgets. With the wxFormBuilder I generated xxx.cpp and xxx.h files. > If I try to compile xxx.cpp with g++ the xxx.h file will be found but > not the incuded header files inside the xxx.h. It seems that the term > "#include <wx/yyy.h>" will not interpreted by mingw. If I extended > the path variable by \wx and modified the trem "#include <yyy.h>" > then the header file yyy.h will be found. I have no idea to solve the > problem Does http://mingw.org/wiki/IncludePathHOWTO give you any clues? -- Keith. |