From: Ralph L. <Ral...@gm...> - 2014-11-26 11:06:21
|
Hi Matej, On 26/11/2014 11:52, Matej Sekoranja wrote: > We’ve just discussed this yesterday. I’ve looked at the code and > changes are not trivial. I’ve patched caSecurity{.h,.cpp} to compile > (on both using preprocessor macros), but then there is putNotify > problem. I will not proceed and I’ll create a new tracker entry. Yes, thank you. Perfect match, since I have started working on the putNotify side of things. >> I was planning to do the necessary changes on develop. >> Are there plans to change the spec of V4 to include C++ parts to be >> working with 3.15? Was that discussed at the telecon? > pvCommonCPP, pvDataCPP and pvAccessCPP, normativeTypesCPP compile and work with 3.15. As they only use the build system. > pvDatabaseCPP fails because of pvaSrv dependency (can must remove this dependency in the future). That's Marty's call. I don't see that happening soon, as he based his example code on pvaSrv, IIRC. Even if those examples are separated out into their own module, that module would depend on pvaSrv. > pvaSrv does not, but this is understandable since it uses core internals. Yep. > Should I attack my changes as a patch file in the tracker or commit to develop branch? Just commit to develop. Thanks a lot! ~Ralph |