Gabriel and Kevron, Regarding downloading dependencies during run time; this was addressing several issues: - Downloading the dependency on demand on the build machines was easier than sending a request to the LF to modify the build environment especially when the moving the dependency up and down in version. This will be addressed if/when we transition to docker for the build environment. - Folks would fail to download dependencies and could not determine what was missing - Folks would download dependencies to the wrong directory - Folks would download the wrong version of the dependencies and report issues as bugs
Regarding unit tests; is 'TEST=0' currently a build option? Regarding a 'make install' equivalent; I agree. Are you recommending the use of your install script? Pat > -----Original Message----- > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev- > bounces at lists.iotivity.org] On Behalf Of Schulhof, Gabriel > Sent: Thursday, June 11, 2015 3:45 AM > To: Rees, Kevron M > Cc: iotivity-dev at lists.iotivity.org > Subject: Re: [dev] HashTag: FixMe > > Hey! > > On Thu, Jun 11, 2015 at 10:33 AM, Rees, Kevron <kevron.m.rees at intel.com> > wrote: > > My iotivity wish list: > > > > - Don't download dependencies during compile time. > > - Don't build unit tests if TEST=0 > > - make install plz > > Seconded. So far, I have > > https://github.com/gabrielschulhof/iotivity/blob/install/install.sh and > https://github.com/gabrielschulhof/iotivity/blob/install/octbstack.pc.in > > but evidently that's a stopgap. > > Cheers! > > > > Gabriel > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev
