On Tue, Sep 21, 2010 at 1:07 PM, Koen Deforche <[email protected]> wrote: > Hey Pau, > > 2010/9/20 Pau Garcia i Quiles <[email protected]>: >> On Mon, Sep 20, 2010 at 8:53 AM, Koen Deforche <[email protected]> wrote: >>> Hey Pau, >>> >>> 2010/9/19 Pau Garcia i Quiles <[email protected]>: >>>> Hello, >>>> >>>> I was going to start packaging Wt 3.1.5 (I've been unable to do that >>>> before due to some health problems) but I found a couple of issues: >>>> >>>> - Wt 3.1.4 and 3.1.5 both have the same soname (23). It's still 23 in >>>> git, too. If you move forward to 25 in git, I will patch the Debian >>>> package so that 3.1.5 is 24. Is that OK? >>> >>> That's okay, yes. I've modified my git copy already. >> >> Only WT_SOVERSION has been bumped to 25, you need to also bump all the >> libraries which depend on libwt > > Oops. I really need to follow my notes on this. Or do it more often :-)
:-) >> I see. That should not be a problem. It should be possible to have a >> CMakeLists.txt with FILE( DOWNLOAD ... ) and ExternalProject_Add to >> replace winst. The only thing you need is something to bootstrap it >> for people using CMake < 2.8. >> >> My proposal: have a (very small) .sh for Unix users and a .bat for >> Windows users which FTP's to the CMake FTP server and downloads CMake >> 2.8, then FTP's to webtoolkit.eu and downloads that CMakeLists.txt. On >> Windows it is possible to automate the FTP download like this: > > That would indeed solve the CMake 2.8 dependency. But you still need > an entirely separate 'installation' procedure to install most of Wt's > dependencies installed by winst, like libharu, libgraphicsmagick, et > al, which are on UNIX './configure; make; make install' projects. ExternalProject_Add was added to take care of all that. There is an introductory article here: http://www.kitware.com/products/archive/kitware_quarterly1009.pdf > So > how much will you be sharing effectively in the CMake procedure for > unix and windows ? Everything but the minimal .sh/.bat to download CMake 2.8 and the bootstrapping CMakeLists.txt. That CMakeLists.txt would be identical (or almost identical) for both Windows and Unix. > Somehow I feel that at this level of winst, everything is different > between UNIX and windows and it is just as convenient to cook up > something specific to windows ? I do not think so. In fact, I think it is a very bad idea. Maintaining two different winst "codebases" would mean different bugs, limitations, implementing everything twice, etc -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
