If I understand right. Currently the json2cbor program does not have support for cross compilation. For this reason we still need to have dat files checked into the code base for cross compilation situations.
The fact that the date files are being modified means that the source .json file was changed and the .dat was not committed at the same time. Anyone that knows more on the subject please feel free to correct me. George -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Mats Wichmann Sent: Friday, July 21, 2017 10:22 AM To: IoTivity Developer List <[email protected]> Subject: [dev] generated .dat files I'm not sure this is working the way it's supposed to. After builds this morning I notice: $ git status -s -uno M resource/csdk/security/unittest/oic_svr_db.dat M resource/csdk/security/unittest/oic_svr_db_prov.dat M resource/csdk/security/unittest/oic_unittest.dat M resource/examples/oic_svr_db_client.dat M resource/examples/oic_svr_db_client_directpairing.dat M resource/examples/oic_svr_db_server.dat Do we really want them modified in place this way? I'd suggest we would want untracked .dat files (targets of the build), and saved generated ones with a different suffix, such that the build either generates .dat's by running the tool, or in case not supported (cross-builds), copies them from the saved. _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev _______________________________________________ iotivity-dev mailing list [email protected] https://lists.iotivity.org/mailman/listinfo/iotivity-dev
