The Android NDK is distributed as a tarball. No agreements to click through. Also, "OSI-approved" is a vague statement to make on the mailing list. Please describe this. Or give me a better search term to use.
-----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Tuesday, May 19, 2015 11:51 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] [Iotivity-infratructure] Build check request for every commit for Android and Tizen platform. On Tuesday 19 May 2015 15:43:05 Morrow, Joseph L wrote: > If you?re looking to make SConscript changes (ie. install the NDK to > an End User?s machine automatically, all you need to do is simply edit > the SConscripts in our repo). Don't do that if there are software licences outside the OSI-approved ones or if there are click-through agreements in addition to the licences. And don't do that if the download is more than a couple of megabytes. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
