On Tue, Sep 22, 2009 at 10:40 PM, Wim Dumon <[email protected]> wrote: > Pau, > > Nice list of ideas! Looking forward to some of them... maybe you > should execute them in reverse order? ;-)
:-) > I actually made the modifications in my working tree to use the > standard FindBoost.cmake of cmake 2.6.4, to test how it behaves on > windows. The result is very good, it found my boost installation > without a glitch. > However, I wonder if it's acceptable to drop cmake 2.4 support yet. It > is not yet very old, and I think there's still a lot of linuces using > it... As we found that boost support in 2.4 is horrible, I want to > come up with something that uses the current system for pre 2.6.4, and > the included thing for 2.6.4 and newer. And that is something I did > not implement yet. Most Linux and BSDs now carry CMake 2.6.2 or newer because that's the requirement to build KDE4. FindBoost.cmake from CMake 2.6.2 and 2.6.3 is still far from perfect, though. IIRC, we (KDE developers) will require CMake 2.6.4 for KDE 4.4, which is due in January 2010, so that should be acceptable. On the other hand, FindBoost.cmake should work fine with CMake 2.6.2, so that's not a problem. Regarding CMake 2.4: something I have not tested but may just work is replacing WtFindBoost.txt with a copy of FindBoost.cmake (it's licensed under BSD, so there's no problem with that) from CMake 2.6.4 (or even CMake CVS, which has some additional fixes) and trying if that works with CMake 2.4. I have skimmed over FindBoost.cmake from CMake 2.6.4 and I cannot see anything obvious which may prevent it from working with CMake 2.4. It would need some testing, though. > > 2009/9/22 Pau Garcia i Quiles <[email protected]>: >> On Tue, Sep 22, 2009 at 8:35 PM, Diego Cantor-Rivera >> <[email protected]> wrote: >>> On Tue, 2009-09-22 at 18:14 +0200, Pau Garcia i Quiles wrote: >>>> On Tue, Sep 22, 2009 at 4:33 PM, Diego Cantor-Rivera >>>> <[email protected]> wrote: >>>> > On Tue, 2009-09-22 at 09:48 +0200, Koen Deforche wrote: >>>> >> Hey Takashi, >>>> >> >>>> >> 2009/9/21 Takashi Yamamoto <[email protected]>: >>>> >> > 1. The examples have a .wt extension. Is it possible to use another >>>> >> > extension instead of .wt (if yes, please state how this can be >>>> >> > achieved) >>>> >> >>>> >> As Zhimin already replied, you are free to rename your applications in >>>> >> any way. >>>> > >>>> > Following up on this question, if you are using Apache then make sure >>>> > that you have this on your configuration: >>>> > >>>> > <IfModule mod_fastcgi.c> >>>> > AddHandler fastcgi-script .your_extension >>>> > FastCgiConfig >>>> > </IfModule> >>>> > >>>> > Where .your_extension is the extension of your executable file. >>>> > >>>> > You set this extension in the CMakeLists.txt file in these two >>>> > statements: >>>> > >>>> > ADD_EXECUTABLE(ProjectBinary.your_extension ...) >>>> > TARGET_LINK_LIBRARIES(ProjectBinary.your_extension ...) >>>> >>>> I see a lot of people do not know CMake at all. Maybe I could make a >>>> very short text (or slides) summary of my CMake slides and it could be >>>> included in the Wt tarball. How do you like the idea? Koen? Wim? >>>> >>> >>> >>> Hello Pau, >>> >>> I am trying to put an example on the Wiki. >>> >>> http://www.webtoolkit.eu/wt/wiki/index.php/Using_CMake >> >> It's a good start but there are some errors and bad practices (for >> instance, you should never type the names of the libraries directly in >> TARGET_LINK_LIBRARIES but call FIND_LIBRARY and use the variable). >> >> I will try and improve the wiki page but I will probably be very busy >> until Friday. >> >> Good news is this Friday I finally deliver of a long project that has >> been a roadblock for me for many things for the last few years. I will >> be on holidays in London most of the next week but I have several >> improvements in mind for CMake and Wt: >> - implementing Perl-compatible regular expressions in CMake (I'm >> already half-done with this) >> - improving FindWt.cmake (support for the COMPONENTS keyword >> introduced in CMake 2.6) >> - improving the Wt's CMake build-system (it could use some cleaning >> and IMHO it could benefit from using the standard FindBoost.cmake >> distributed with CMake 2.6.4 and newer, which is very good) >> - writing a web-based FindXXX.cmake which you could tell "I want to >> you find libfoo, whose most significant header file is >> /usr/include/foo/foo.h, etc). That would be both useful and a good >> example - hint hint. >> - creating a Wt widgets plugin for Qt Designer, so that you can >> visually build the interface. This is quite easy, actually. It would >> also require an uic-wt but that should not be difficult either (Koen, >> did you make any advance in the W_PROPERTY stuff?) >> - Implementing the webkit integration described in >> http://www.webtoolkit.eu/wt/wiki/index.php/Ideas_for_Google_SoC (that >> was something we came up at dinner at last year's FOSDEM, I think it >> would be very nice and useful) >> >>> I noticed that you can't upload images. Is it possible to change this >>> setting? Otherwise I can use links to any of the mainstream image host >>> providers. >> >> I'm not associated with EmWeb (other than being a happy user :-) ) so >> I cannot help you with that. As a user, I would prefer if it were >> possible to upload images to webtoolkit.eu and not depend on a third >> party. >> >> -- >> Pau Garcia i Quiles >> http://www.elpauer.org >> (Due to my workload, I may need 10 days to answer) >> >> ------------------------------------------------------------------------------ >> Come build with us! The BlackBerry® Developer Conference in SF, CA >> is the only developer event you need to attend this year. Jumpstart your >> developing skills, take BlackBerry mobile applications to market and stay >> ahead of the curve. Join us from November 9-12, 2009. Register now! >> http://p.sf.net/sfu/devconf >> _______________________________________________ >> witty-interest mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/witty-interest >> > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
