Dnia poniedziałek, 3 października 2016 08:20:01 CET Thomas Baumgart pisze: > Hi, > > On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote: > > On Sunday, October 2, 2016 9:31 PM, Jack wrote: > > > I could see the clientuid box on the ofx details page, I couldn't enter > > > anything > > > > If the box cannot be edited, it seems that the KMM build did not recognize > > that libofx supports CLIENTUID, and so disabled the box. And if that's > > true, then even if you hand edit the KMM file to add the CLIENTUID, KMM > > won't pass it to libofx because it thinks it's not supported. > > Well, the detection was fine, but the build environment did not tell the > cmopiler about it. This is now fixed in the 4.8 branch. > > While I was at it, I added a clientuid field to the setup wizard. Can > someone test that please? I don't have such an account at hand. > > > As an aside, the CLIENTUID detection during config did not work for me on > > my Windows build (it says "No" support). I figured it was a Windows > > problem, so I just edited my copy of the KMM source to use CLIENTUID > > anyway. Look for #ifdef/#ifndef LIBOFX_HAVE_CLIENTUID in the ofximport > > folder. > > Well, how would one fix the detection on windows. We do use cmake features > to do that.
It should be fixed by D10125.
