Klaas Holwerda wrote: > Malcolm Nealon wrote: > >> Klaas Holwerda wrote: >> >>> Malcolm Nealon wrote: >>> >>> > > I understand, but this makes no sence to cmake. > Cmake already generates makefiles for MSYS or Mingw, and they should already > fit > mingw32-make. So there is no need to have a makefile.gcc. > We should be able to run cmake, and next mingw32-make, and that all. >
I understand you now. > wxWidgets needs to have a difference in makefile because the are generated in > put into CVS, this is not the case with Cmake. > Think of cmake as a replacement for makefiles, like a Cmake compiler for > platform/compiler generated makefiles. > Right. I'm beginning to get there. >> If I understand your question, the wxWidgets libraries are then named in >> the unix way, when built using gcc makefiles, libwxmsw28.a (monolithic >> build), libwxmsw28_aui.a (non monolithic build). This shouldn't come as >> a surprise, since I would imagine that since the gcc toolchain is >> available on many platforms, that there would be a standard naming >> convention for it's own libraries etc. >> > > Exactly. But still something that the wxart2d cmake files did not anticipate. > Because i think when using wxGTK, on windows, i will get names like > libwxgtk28_aui.a, but will check this when i get home. > > OK >>> But from what i see above, wxArt2d detects in this in a Unix manner, els >>> ethe >>> libs would have bin called like on VC2005. >>> >>> >> I am not sure how or where it does it, but I would guess that there is >> a section which is related to gcc compilers, and that does all the >> naming. It doesn't matter how or where the gcc compiler is called >> (mingw, wxDev-C++, configure/make), it uses the same command line, same >> switches, etc (IIRC). Even the MSYS makefiles follow the command line >> for gcc compilers. Somewhere in the files there is a line for each .cpp >> file looking _something like_ >> > > I don;t want to knwo, i can solve it easily in cmake, as sson as i knowm what > is > required. Makefile is like assembler to me, and cmake like programming in C++. > Its is 20 years ago taht i programmed assembler :-) > OK. However I guess you'll need to merge two parts of your current cmake files. One part will be the section that is used by Borland/microsoft makefiles for detecting settings, the other will be the makefile generation for mingw. If all is well it should produce windows based makefiles for building using the local copy of the gcc toolchain. Am I correct in assuming that currently the mingw section needs the wx-configure program to work correctly? But that the Borland and Microsoft sections don't, and work in a different way? >>> So Cmake uses the output of wxconfig here. And from that is get the idea, >>> that >>> libraries generated by makefile.gcc are named the unix way, but i am not >>> sure? >>> >>> >> They are. But again this is simply because ALL versions of gcc on ALL >> platforms use that naming convention. >> > > Oke, but in principle it is about the linker in question, so i think that > requires -libXXXX as naming. > > yes, the libs should have what you termed unix naming. >> The $64000 question. >> > > Right, i keep searching, the worst thing is that it only is in release mode > :-( > Good hunting. Best regards Mal ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Wxart2d-users_dev mailing list Wxart2d-users_dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
