Klaas Holwerda wrote: > Malcolm Nealon wrote: > >> I could send you the files I created when compiling each module, you >> could possibly point me in the right direction. >> > > That is oke. > OK that I send them or just "never mind, it's ok"?
>> I prefer just having a file that can be compiled, say for example that >> wxArt2d came with its own makefile.gcc and config.gcc >> > > This will not happen i think. > Not unless there is a concerted effort to create the bakefiles. > In principle running cmake on any platform is simple too. > You are used to a certain way of working. The bakefile approach is to support > all the different ways of compiling on all platforms, and generate makefiles > for > that. They are added to wxWidgets, and that what the users sees. > The problem is that this approach needs all the knowledge on all make systems > for all platforms, next to writing and maintaining bakefile itself. > One needs a lot of man power to achieve that. And even if documentation would > be > oke, it still is a struggle to get it working for your own projects. > I can understand this, which was why I was thinking of hijacking the wxContrib stuff. In essence (assuming I know what I am talking about - a BIG assumption) wxArt2d is just a library, just as the contrib stuff is. It has more dependencies, but basically it is the same. If the wxContrib bakefiles can be used (along with a bit of the wxWidgets stuff to make all the libraries at once) then it shouldn't be much work. Of course this is only going to be realistric if someone does the work. I'll have a look, and see if my reasoning is sound. > Like in wxLua, one needs to know about autoconf and things like that. So its > is > not just bakefile to learn, but also the makefiles that it outputs, need > tuning > enough. > But, having only very briefly skimmed the surface of it, haven't the wxWidgets boffins already done the lions share? Shouldn't it be relatively easy to build upon their work? Could you enlighten me as to what "tuning" is needed? > Also maybe bakefile is a great system, it still depends on the wxWidgets > group > mainly. And if Francesco would not have spend so much time to make it at > least > useable for other projects (wxLua wxCode), the situation would still be as it > was 3 years back. > I agree. > Cmake does generate the makefiles on the user side. <SNIP> For instance KDE > is now > using Cmake, which is huge, and for me the prove that nothing is wrong with > Cmake. Its just different from typing make. > > The main thing for me, is that i have only 24 hours, which is hardly enough > for > wxArt2d. So i cannot spend my time on bakefile and all that comes with it. > Cmake i can manage more or less on my own. And when there are problems there > is > help. > I understand. >> I wouldn't need to know how they were produced, just that they are >> correct, and that I can build the libary using them. >> > > If wxArt2D had some more people actively helping in this area, Cmake would > just > work. And the compiled samples also on whatever cygwin/mingw etc. also. > > I certainly as a user that it just works. > But as a developer ( mainly on his own), i can't do it in a lifetime. > Just to make sure we understand what the real problem is :-) > > Its not Cmake or bakefile, its a matter of maintenance, manpower etc. > I understand. >>> First we need to be able to run samples on MSYS etc. in release mode. > > Just install MSYS, add mingw to it. It all on the mingw site. And not so > complicated. Once you have that, add Cmake (msw) to a bin directory there in > mingw. And set WXWIN on the commandline. run CMakeSetup etc. I'll give it a go. Would the compilation files and results I have help here then? There should be one for each module, you could look at the compiler output for one of the modules, maybe this would offer some help as to where (or more accurately what) is possibly causing the failure? By the way, I have VS2008 express. I managed a debug build with no errors and almost no warnings, and tested several samples, they ran. 1>-- Configuration from C:/wxWidgets-2.8.7 1>-- wxWidgets_USE_DEBUG : ON 1>-- wxWidgets_USE_UNICODE : OFF 1>-- wxWidgets_USE_SHARED : OFF 1>-- wxWidgets_USE_UNIV : OFF 1>-- wxWidgets_FOUND : TRUE 1>-- wxWidgets_INCLUDE_DIRS : C:/wxWidgets-2.8.7/include;C:/wxWidgets-2.8.7/lib/vc_lib/mswd;C:/wxWidgets-2.8.7/contrib/include 1>-- wxWidgets_LIBRARY_DIRS : 1>-- wxWidgets_CXX_FLAGS : 1>-- wxWidgets_USE_LIBS : gl;aui;stc;qa;xrc;html;adv;xml;net;core;base;png;tiff;jpeg;zlib;regex;expat 1>-- Could not find existing antigrain library, will use builtin library instead 1>-- Configuring done 1>-- Generating done 1>-- Build files have been written to: C:/wxArt2d_ms2008 I had to change several options in the generated project (add a preprocessor - _CRT_SECURE_NO_WARNINGS I think) change the run time library option to Multi threaded debug, and turn off manifest creation in the Linker section of the executables projects, for some reason the project forgets this every time I reopen it as well as, ignore specific library MSVCRTD.lib, and then build. 5>genprop.obj : warning LNK4221: no public symbols found; archive member will be inaccessible warning C4996: 'stricmp': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _stricmp. See online help for details. warning C4996: 'hypot': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _hypot. See online help for details. 15>.\wxart2d-config.c(37) : warning C4013: 'system' undefined; assuming extern returning int 15>.\wxart2d-config.c(52) : warning C4996: 'strdup': The POSIX name for this item is deprecated. Instead, use the ISO C++ conformant name: _strdup. See online help for details. I think that this is it. Perhaps there could be some change to the required cMake files to perform these changes? Then I could build wxArt2d under VS2008 express with no errors and no warnings. 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
