Hi,
On Monday, 2011-08-22 14:46:57 +0200, Jan Holesovsky wrote:
> > The cleanest solution (to me) is to have icu produce icui18n.lib
> > instead of icuin.lib, but I'm guessing there is a reason why MSVC
> > generates icuin.lib with the '18' stripped out?
>
> Even the up-stream icu produces icuin
Hi Kohei,
On 2011-08-20 at 10:33 -0400, Kohei Yoshida wrote:
> The cleanest solution (to me) is to have icu produce icui18n.lib
> instead of icuin.lib, but I'm guessing there is a reason why MSVC
> generates icuin.lib with the '18' stripped out?
Even the up-stream icu produces icuin.* when build
On Sat, 2011-08-20 at 10:33 -0400, Kohei Yoshida wrote:
> After many hours of hair-pulling investigation, I've come to find out
> that both icu and cui modules produce a static library named
> "icuin.lib"
Ah, excellent. I'd been baffled by that a load of times. I could never
see what the problem i
> After many hours of hair-pulling investigation, I've come to find out
> that both icu and cui modules produce a static library named
> "icuin.lib",
Ah. Darn.
> The cleanest solution (to me) is to have icu produce icui18n.lib
> instead of icuin.lib,
Yeah, I tend to think so, too, now.
> but I
On 20 August 2011 16:33, Kohei Yoshida wrote:
> So, I was looking into a mysterious build breakage in forms (on
> WIndows). It would fail at link time due to missing external symbols.
> It was expecting to find those symbols from icuin.lib, which is a
> static library file generated from the icu
So, I was looking into a mysterious build breakage in forms (on
WIndows). It would fail at link time due to missing external symbols.
It was expecting to find those symbols from icuin.lib, which is a
static library file generated from the icu module.
The funny thing is, when I do
cd icu
rm -rf
