> <snip> > See if you have a ".dat" file (or a bunch of individual files) in > blib/lib/icu/2.6.1 (relative to your parrot source root). If not, then > that's what's going on. Right now, I have that path hard-coded--of > course I need to pull that out into a config--but it probably means > that either the data files aren't getting created, or just that they > are in a different location. Glancing at your icu.pl patch, it may just > be missing moving the .dat file (or, maybe creating it too). > They are missing, and in fact weren't even being created. Turns out I'd somehow managed to miss a line out in the makefile, namely the one that made the data. D'oh.
I added it in, but this gave rise to new problems. The .mak file (in icu/source/data) was missing some paths so some of the tools were not being found. That was easily fixed, and now it gets quite a way through making the data, until it hits a point where it starts giving errors like this:- -- Making Locale Resource Bundle files ..\..\locales\root.txt:39: warning: %Collation could not be constructed from CollationElements - check context! ..\..\locales\root.txt:37: parse error. Stopped parsing with U_INVALID_FORMAT_ERROR couldn't parse the file ..\..\locales\root.txt. Error:U_INVALID_FORMAT_ERROR ..\..\locales\ar.txt:16: warning: %Collation could not be constructed from CollationElements - check context! ..\..\locales\ar.txt:14: parse error. Stopped parsing with U_INVALID_FORMAT_ERROR couldn't parse the file ..\..\locales\ar.txt. Error:U_INVALID_FORMAT_ERROR ..\..\locales\ca.txt:12: warning: %Collation could not be constructed from CollationElements - check context! ..\..\locales\ca.txt:10: parse error. Stopped parsing with U_INVALID_FORMAT_ERROR -- Any ideas? > [**] There are 4 or so options for how to package the ICU data--into a > dynamic library, into an archive library, as a bunch of separate files, > or as a single file. Any should work, but the last two are faster to > build, and a bit more flexible. > Looking at the makefile, I believe it would package the data in each of these ways, then we'd just copy the .dat into the appropriate place. Once I've got it to actually work, I'll see if I can get it down to generating the .dat only. Jonathan
