Klaas Holwerda ha scritto: > But somehow people think that a configure srcipt on Unix is just fine, but on > windows it is not allowed. on windows you can do very limited tests since there are no standard paths: the user could install his libs anywhere he wants. In C:\programs or somewhere else.
Env variables like WXWIN and "path options" like WX_DIR is the way I solve this problem in bakefile... >> Cmake AFAIR is not object-oriented. Bakefile is. And as you know C++ can >> be more powerful than plain C... > > Cmake is written in C++, so i think you mean XML is object oriented?? yes, XML is (partially) OO. > I miss to see this OO, for me both or about targets and would you do with > them. when I say there's OO concepts in .bkl files I mean that you can inherit from templates defined in other places your own template/target. Ok, no polymorphism / function overloading, since there are no functions, but still there's the "inheritation" logic which is OO. >>> How often did i need to delete my wxLua checkout, and check it out complete >>> again, just to make it compile. >>> Else there are left overs after clean, which makes it impossible to compile. >>> Cleaning up things properly seems to be difficult. >> a "make clean" removes all stuff which has been compiled, I've never had >> a problem with that. > > I do a new checkout now and then, and compile again. And things went wrong > several time in the past. > And that after telling John it did not compile, with weird errors. And a > clean did not help. well, some errors are obviouly not because of the build system but because of the sources not tested with some cfg/compiler, like for recent msvc2005 troubles. >> You can post me a list of files which are _not_ cleaned by "make clean" >> however. > > Next time i have it, i will start a search. Its not a known recipe for > trouble yet :-) ok, thanks >> I proposed to recode wxCode website to be entirely based on those >> package descriptors (which would allow faster rendering of the wxCode >> pages, automated releases, etc, among other things). But I got no reply >> to that mail. Maybe because it was a very very long mail (and we are all >> bored by all that text :)). I'll retry shortly. > > I read it, but i think every one is just to busy to do it. > Maybe a tutorial, and not an email. Email pass by and are easily missed/lost. > Making twiki pages, is more permanent. But i must be carefully, because it > might be there already :-) no wiki pages, yet. But the tutorial idea is good. I'll retry shortly presenting it in that way. > I am planning to use TWiki for wxArt2D, which is very advanced. in case you don't know SF is about to launch a centralized wiki service using WikiSpaces. I'm part of the beta team for that feature. You can look at a test wiki for wxCode at: http://wxcode.wiki.sourceforge.net/ it still suffers of some glitches (e.g. google AD encroach the wiki area) but it's not bad. >>> People are using wxArt2D in Cmake mode, for there own project. They would >>> need to switch too, if they want to stay >>> platform independent, or at least something like a wxart2d-config would be >>> needed. >> I don't think that if bakefile replaced cmake in wxArt2d, then those >> project would be forced to switch, too. Why should they? >> Output libraries would get named&installed in the same way... > > Its not about libraries and headers. > Its about generating makefile/project files for their own code. > For Cmake i made a template, which makes a small project, which the users can > use as a start, and finds wxWidgets (used > to build that wxArt2D), find wxArt2D, and all thirdparty stuff. Next to that > all settings for options ( the ones that > where used ). > You can compare it with what we wanted so much from wxWidgest. > > Or do you really think the users likes to write his makefiles/project files > from scratch? well, using newer wxpresets it should not be difficult to create a project which uses wxArt2D even writing the bakefile from scratch (given wxArt2d respects the usual conventions on naming etc). However I didn't think about the 3rd party libs, like freetype and agg. Those could be a source of problems, true. >>> I wait patiently. >> Let's finally remove them. >> I have no much free time and dividing my efforts on too many things is >> not going to be a Good Thing for my projects. > > Oke. I understand, we have something working for wxArt2D even if its based on > Cmake ;-) > And i am able to maintain it myself. > We know very well now how we want to organize things in term of library names > etc. > If we/i ever continue, with bakefile, i must first have enough time to > understand it, and maintain it to a certain degree. sure > > Tag the whole thing before you do, so we can always find it back. good idea. I've tagged the sources and removed the bakefile files from CVS. 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
