From: Alex P. <pes...@ma...> - 2012-07-24 13:15:54
|
On 07/23/12 17:48, Adriano dos Santos Fernandes wrote: > On 23/07/2012 10:34, Alex Peshkoff wrote: >> On 07/23/12 14:41, Adriano dos Santos Fernandes wrote: >>> On 23/07/2012 06:49, Alex Peshkoff wrote: >>>> Somewhy it happened that in my trunk I have platform.h in >>>> extern/icu/source/common/unicode. No idea how did it arrive in that dir >>>> (certainly, not under version control). As far as I know about Android, >>>> icu libraries are present in default device's setup. But question comes >>>> - what is best way to access them when doing cross-build? >>> If it's not in the NDK, then the library is unsupported and may not be >>> in all versions. It's there just to the OS. >>> >>> So in this case we should supply it. But for client only we would not >>> need ICU. This is a problem of our "common" library who have server-code >>> which is never called by the client. >> Hmm... >> I do remember that I had to add CharSet.cpp to common in order to build >> client. Will recheck. >> >> > The problem is that some things (specially unicode_util) was added to > common, but in fact, it's a piece needed only in engine and intl libraries. > Do you want to say that a member of static library, not used to resolve symbols during link, will anyway cause errors when it references non-existent library? I've always thought that ld is not so foolish. |