Just because it was super-easy for me to fix: https://github.com/apple/swift-corelibs-foundation/pull/587
That should allow C++ to be built if desired into CoreFoundation. However round tripping that into the Darwin version of CoreFoundation may be a bit cagey. > On Aug 23, 2016, at 4:53 PM, Henry Betts <henry.be...@btconnect.com> wrote: > > >> On 23 Aug 2016, at 16:58, Philippe Hausler <phaus...@apple.com> wrote: >> >> Is there a specific version of ICU that we need to pick that functionality >> up? As it stands we don’t have a upper version limit on ICU but if we had a >> portion of the ICU source in CF it would probably mean that we would get >> symbolic conflicts when linking against versions that already had that. > > > Looks like the C++ MeasureFormat (and friends) have existed since ICU 3.0, > although they have not yet got around to implementing a C interface. I don’t > think symbolic conflicts would occur, since, if ICU did eventually introduce > the C interface, I assume that it would use just a “u” prefix rather than > “ua”. Not sure if that’s what you meant. > > Alternatively, I suppose we could just bypass uameasureformat, and interact > with the c++ api directly in CF, since it looks like it’s going to have to be > setup to compile c++ anyway. > > Henry _______________________________________________ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
