Here is how 1.3 behaves with respect to .dat files.
------------------------------------------------------------------ The build does not generate any new .dat files as far as I can tell (i.e. json2cbor not run at build). * Since no new .dat files are created in the src tree, they don’t show up as modified with git status The build does copy over .dat files from the src locations to the destination location (out/…) * This places proper .dat files in the samples directories etc. It is assumed that developers will keep the .dat files up to date with the corresponding .json files, and commit them. ---------------------- Somethings is different between 1.3 builds vs. current master RE generating .dat files during build. The 1.3 approach seemed to work pretty well to me (i.e. don’t generate .dat files during the build). As it is now, you have to re-checkout all the generated .dat files so they don’t get caught up in your commits. Kind Regards Steve > On Mar 5, 2018, at 9:52 AM, Philippe Coval <philippe.co...@osg.samsung.com> > wrote: > > > > On 03/05/2018 03:31 PM, Wouter van der Beek (wovander) wrote: >> Sounds like an issue.. > to be reported ;) >> The python works great for creating the introspection files as part of the >> DeviceBuilder tool chain and works fine with the CTT. >> I have tried to use exactly the same sequence for the security files, but I >> never got that to work... not sure what is different and why it should be >> different. >> > > Python tool will be welcome for sure, but I will not recommend to use it. > Relying on 2 implementations to produce .dat files is subject to inconstancies > we already faced this in the past (and still today), when all .dat files were > not updated after changes. > > Also something which is bugging me is that some dats files are modified once > tests are run, and spotted as different, > maybe we should avoid to touch .dat files in tree after they generation. > > Regards > > -- > mailto:philippe.co...@osg.samsung.com gpg:0x467094BC > https://blogs.s-osg.org/author/pcoval/ > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev@lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
