Steven R. Loomis
Steven R. Loomis
> > > no, the issue is more complicated than my PR did. > > > > > > Do you have more detail? > > It require more detail...
@richgillam OK to merge this and get it off the books?
@evanmiller makes sense, thanks for fixing this very longstanding issue!
Hi. By the way, as I noted https://github.com/mesonbuild/wrapdb/issues/950#issuecomment-1490972572 there's a sources.txt and dependencies files, which should be used for getting the source files. My cmake branch used it. [gencmake.py](https://github.com/srl295/icu/blob/icu-srl/7747cmake/source/test/depstest/gencmake.py)
@clemenswasser ^ that link to gencmake.py goes to my old branch. And by old i mean old.
> My current guess is, that there is some sort of binary patching of the U_ICUDATA_ENTRY_POINT variable happening during the "makedata" step, which doesn't happen in my CMake port. Here's...
@ceztko this is for a bootstrap from source (i.e. git). I hate doing rework too, but what else would you do? if you have a release tarball, it has `source/data/in/icudt72l.dat`...
These are two different issues. gencmake.py is for the code structure. It's a way to slice up which .cpp's need to be included with finer granularity than the library. The...
> > The reason for the double build in the case of cross platform has to do with the original data, which needs ICU source to run. It's really a...
> > As a matter of curiosity -- any particular challenge this causes, other than the general need to possess both a host and a build compiler? > > This...