On Tuesday 19 April 2011 at 16:47 Philippe Makowski wrote: > > Where ? > the only link I found is : http://site.icu-project.org/download > and with this we can't do a 'one click install'
We wouldn't want to do that anyway. The icu binaries would be specific to a particular version of Firebird. I doubt that we would want to deploy them as an assembly to <sysdir>. And one reason for moving to MSVC10 is to get away from dependancies on assemblies anyway. > we must provide binaries inside our Windows package :( > Yes, that is right. I don't object to agreeing on a specific version of ICU for each release. We would just change the build script as required. (Presumably we will need .lib files.) Our main problem is likely to be finding icu binaries built with MSVC10. Not much would change as far as packaging is concerned. We would just include the icu dlls as now, except their location at package time will / may be different. Of courses, we may get lucky and ibm will have upgraded their ridiculous icu build system and we could just incorporate it again into the windows build. However, if it hasn't been changed it would require a ton of work for each icu version, which is one of the reasons why we haven't upgraded icu. Paul -- Paul Reeves http://www.ibphoenix.com Specialists in Firebird support ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
