On Fri, Apr 29, 2011 at 10:49 AM, Vlad Khorsun
<hv...@users.sourceforge.net> wrote:
>>> 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.
>
> ICU 4.6 (more exactly icu4c 4.6 and latest 4.6.1) are built using MSVC10,
> so
> this is not an issue.
>
> BTW, we still have no MSVC10 at our build farm, but this is another
> question...
>
>> 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.
>
> One note. Binary packages at IBM site
>
> http://download.icu-project.org/files/icu4c/4.6.1/icu4c-4_6_1-Win32-msvc10.zip
> http://download.icu-project.org/files/icu4c/4.6.1/icu4c-4_6_1-Win64-msvc10.zip
>
> contains relatively "big" ICU libraries. Size of 3 dll's needed for Firebird
> is more than
> 16MB, the biggest is icudt46.dll (14.4MB) which contains a lot of unused by
> FB data.
>
> Should i said that whole FB folder have similar size ?
>
> Here http://apps.icu-project.org/datacustom/ we can see what could be
> removed
> without any harm.
>
> We should decide (at least for Windows)
> a) will we provide ICU libraries
> - within our packages (as with FB2.x), or
I vote for this one
> - ask users to download ICU from IBM site, or
Asking users to download separate package is prone to errors : there
will be a flood of questions : where do i download ... firebird
doesn't work out of the box
(matching icu versions hell)
> - provide separate package with just 3 DLL's we need
it should be optional and for people who want slim firebird
> b) will we provide default ("fat") ICU libraries or our customized ("light")
> version ?
Provide fat icu in first stage and if is requested make it light (hdd
space/bandwidth is realy cheap these days) and doesn't worth to spend
to much
time in overoptimizing the used space
Creating a light package is a good idea for embedders but that want to
create small packages but that should be optional package
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
