Leopold Toetsch wrote:
Jeff Clites <[EMAIL PROTECTED]> wrote:
ICU somehow manages (optionally?) to suffix all it its symbols with the
version number, automagically (meaning, they don't look that way in the
source or the headers).
urename.h is responsible for this. All the symbols get a vers
I think the Cygwin port for using static libraries has to be finished
for ICU. The current ICU CVS snapshot should be better suited for
static libraries, but it's not completed yet. Help is always
appreciated on this matter.
You could try to set CPPFLAGS=-DU_STATIC_IMPLEMENTATION before you r
Dan Sugalski wrote:
At 6:03 PM -0600 4/21/04, kj wrote:
Hello folks,
This will be of interest to only a few people, but it will be good
to have it in the archives for when we need it.
Here is a list of Korean character sets that represent hangul
(Korean symbols) and hanja (Sino-Korean):
Your concerns are valid for versions of ICU before 3.0. ICU 3.0 will
allow you to build with Cygwin with gcc or MSVC's cl compiler.
The toolutil library is located in icu/source/tools/toolutil. If you
used the --disabled-shared configure option as Parrot's README states
(not ICU's readme), yo
Jeff Clites wrote:
On Apr 15, 2004, at 11:12 AM, George R wrote:
I went with the --with-data-packaging=archive initially for 3
pragmatic reasons: (1) it seems to take a really, really long time to
build them into a library, and (2) once parrot "ships", if we use
--with-data-packagi
Hello Perl6 people,
I couldn't help but notice that you were talking about ICU on this
mailing list. Let me interject with some suggestions.
I should mention that ICU 2.6 can build a static data library. I
recommend that ICU be built without the --with-data-packaging=archive
configure option
