On Apr 6, 2017 3:13 PM, "Daniel Mihai" <Daniel.Mihai at microsoft.com> wrote:
I?m not sure how you define ?standard production build?, but the answer is probably yes i'm not sure either ;) but mainly because i'm not sure what you'te proposing. let's say i'm an iotivity noob. i download, compile, and install. does my installation include the experimental bit? *From:* Gregg Reynolds [mailto:dev at mobileink.com] *Sent:* Thursday, April 6, 2017 1:11 PM *To:* Daniel Mihai <Daniel.Mihai at microsoft.com> *Cc:* uzchoi at samsung.com; Dave Thaler <dthaler at microsoft.com>; iotivity-dev at lists.iotivity.org; Mats Wichmann <mats at wichmann.us> *Subject:* Re: [dev] Public and Experimental Public C APIs On Apr 6, 2017 2:09 PM, "Daniel Mihai via iotivity-dev" < iotivity-dev at lists.iotivity.org> wrote: Should we start with the following definitions? 1. All C functions included under out/<path_to_IoTivity_SDK>/ are Public APIs 2. All C functions included under out/<path_to_IoTivity_SDK>/experimental/ are Experimental Public APIs ok just to be clear, are you proposing that out/<path_to_IoTivity_SDK>/experimental/ should be part of the stsndard production build? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170406/a79a01a5/attachment.html>
