Can't link "dynamic" and "full" about cld2

[GoogleCodeExporter]

The dynamic data tool was written with Chromium in mind, which is why it 
directly references the Chrome data structures. The simplest fix is probably 
for us to provide empty tables with these names for non-Chrome builds. 
"Simplest" != "Cleanest". The clean solution here is to make the set of tables 
that are included in a dynamic build completely configurable, but that requires 
the format of the dynamic data file to be significantly altered to include 
metadata about which tables are included and in which order.

You should be able to work around this issue temporarily (if it is blocking 
you) by copying and pasting one of the quadschrome* sources and emptying it of 
all data, then linking against that instead.

Original comment by [email protected] on 15 May 2014 at 4:21

[GoogleCodeExporter]

doppelbauer: Did this work for you? If so, I'm happy to add a dummy file to the 
repository that will let you avoid the manual workaround.

Original comment by [email protected] on 27 Oct 2014 at 8:43

[GoogleCodeExporter]

Hello,
Maybe it is better to close this issue - it's not a real problem.
Thanks a lot for the excellent cld2!
Markus

Original comment by [email protected] on 27 Oct 2014 at 8:53