Klaas Holwerda ha scritto: > Francesco Montorsi wrote: >> Hi, >> today I've tried to compile wxArt2D with cmake. Here are some of my >> annoying complains :) >> >> (I'm on Ubuntu linux) >> >> 1) I run "cmake ." in wxArt2d. Nice, it shows me some checks etc and >> says build files are ready. Great. I just wonder which config of my many >> wx builds it has chosen since it does not tell me that. Not much of a >> problem however. > > Oke, i should be able to do something about that. > I myself always use ccmake, and there the options are there to choose the one > i want *debug, unicode etc. > But you are right, it is good to see that it did indeed get the right one. right. It would be nice to show (as I do with configure scripts in e.g. wxLua) a final message telling the user which wx configuration has been selected and the main configuration options chosen for wxArt2d itself.
>> 2) run "make" and after a while I get: > >> so cmake-unrelated question: does wxArt2D really really really needs >> wx compiled as --disable-std_iostreams ? It's a pain for me: I have lots >> of wx builds done without that option and reconfiguring and recompiling >> wx with it is going to take a lot of time... > > Yes this horrible. And and comes a long way without --disable-std_iostreams. > The problem is that in early days this was the default on windows and unix. > Now it is the default on windows, and on Unix not. > So i am forced to maintain two ways of handling streams that are rather > different. > I already made a wrapper to handle both the same way within wxArt2D, but it > is a nightmare. see my other mail about this. > > Its a work in progress:-( But i think it works fort ascii/xml based files > already, only the binary files is problematic. > >> the other warning about deprecated header couldn't be fixed? > > I think it can, i myself always use --disable-std_iostreams, so i think i did > not notice it. > >> >> 3) ok, I remember that I have an installed build of wx2.8 (instead of >> wx29) which does not have those UTF8 changes and thus should work with >> wxArt2D. > > UTF8 changes?? I need to check what/where those are on my fedora machine. well, they are still doing various ones and so things are not stable yet. However there's a nice wiki page (which is on my TODO list for a careful reading) which describe the required changes. >> I do "cmake -i ." and start to reply to all questions done by cmake. > > ccmake is much easier. right, it's nice. I'll keep that in mind. >> none of them allow me to select as wx build the one with version 2.8... >> why is WX_VERSION-cmake-equivalent missing? > > I detect it automatically from wx-config. > I think i need to change that if the user did set it, it should not be auto > detected, instead only tested. > As you see you are the expert in this field :-) that's important because not only I have several installed builds of different wx configurations of the same version - I also have installed builds belonging to 2.6, 2.8, 2.9, etc. The user should be able to specify to the build system an univoque set of options to identificate a wx build. >> 4) I do "cmake clean" because I want to reconfigure totally the wxart2d >> package. With surprise I find that even after "make clean" doing "cmake >> ." does not give the same output of the first time. > > What do you mean different in output? when I did run it the first time it did all configure checks. Now when doing "cmake ." it only regenerates the build files without rerunning any check. This gave me problems as I wanted to reconfig wxArt2d to force it to use another wx build. I've now solved pressing "c" in ccmake. > Some cached files >> are kept. How can I remove them (without doing it manually)? > > ccmake has a delete cache i believe, at least on windows that is the case for > CmakeSteup.exe I didn't found any delete cache command even in ccmake. > >> >> I know all are simple/dummy problem and not strictly related to cmake, >> but still I think this feedback may help to improve the build system of >> wxart2d... > > Of course thanks a lot! BTW I'm going to do some small commits to wxArt2d sources to fix Unicode builds (i.e. some atoi => wxAtoi and some missing wxT() macros)... Francesco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wxart2d-users_dev mailing list Wxart2d-users_dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
