Hi, My dad passed away last year please remove him from this thread.
Thank you On 11 June 2018 at 04:40, Day, Julian <jcd...@mail.usask.ca> wrote: > Just a quick note: this seems to solve the issue. I uninstalled Anaconda > (not using it at the moment), installed v61.1 of ICU-C, and I was able to > compile and link xerces 3.2.1 without any errors. > > Thanks, > Julian > > ________________________________________ > From: Day, Julian > Sent: June 10, 2018 1:33:16 PM > To: c-users@xerces.apache.org > Subject: Re: Problems building latest Xerces with Win10 and MSVC > > Hi Roger, > > It seems as if the version of ICU I have is part of my Anaconda > installation. > > I'll get a newer version and try the process from the beginning. > > Thanks, > Julian > ________________________________________ > From: Roger Leigh <rle...@codelibre.net> > Sent: June 10, 2018 1:05 PM > To: c-users@xerces.apache.org > Subject: Re: Problems building latest Xerces with Win10 and MSVC > > On 10/06/2018 16:56, Roger Leigh wrote: > > > Firstly, I think you have found a bug with a combination of > > configuration options we haven't explicitly tested with VS2017, namely: > > > > - icu > > - char16_t as XMLCh > > > > ICU is expecting wchar_t, and we need to explicitly reinterpret_cast > > from e.g. const char16_t * to const wchar_t *. > > > > I thought we had already fixed all these cases, but there are so many > > different ways you can configure Xerces-C++, it's quite possible I've > > missed this particular combination. > > Actually, just to follow up, new versions of ICU switched to char16_t a > few releases back. I think if you used a newer version of ICU, you > would find this would work seamlessly. > > However, we probably want to add appropriate casts to the ICU type so > that it works with all ICU versions. > > > Regards, > Roger > > >
