As described in my last blog entry, the main show stopper was getting the ICU library compiled with the Haiku GCC 4.1.2 cross compiler.
After reading some documentation and a lot of trial and error, I finally got Haiku's GCC 4.1.2 to compile code outside of the Haiku build environment. I will document how to do this within the next week, as there are a few gotchas.
Once I had that working I was finally about to successfully run ICU's configure script, and most of the build went fine until the data directory. The data directory uses some code generators to do its work, but the code generators were compiled for Haiku, yet I was running them on Linux. I emailed the ICU mailing list for some help, but alas, received none. It seems I'm doomed to be a pioneer and figure out all my problems alone for this project.
Well it actually was pretty obvious to just build ICU for Linux and then copy over the needed code generators, and this is what I did. After this the build for ICU seemed to go fine.
But when I went to test, there was some odd error about a missing symbol in one of the ICU libraries! Argh! So I decided to take a break and sleep on it, and then today I looked again. It turns out the library from the infamous data directory did not compile right the first time, so I tried it again, and it finally worked!
See the attached screenshot for some exciting textual output.
- Haiku field trip report - January 2020
- Google Code-in 2019 finished
- No, I'm not Haiku's lead developer
- Haiku monthly activity report - 12/2019
- Haiku almost-monthly activity report - October and November 2019
- Haiku monthly activity report - September 2019
- Node.js now available in Haiku
- Haiku monthly activity report - 08/2019
- GSOC 2019 Final Report
- Haiku Activity Report: Performance Edition