Kevron,

If we are sharing wish lists, I would add:
- Make package and dev-package to create a canonical iotivity and iotivity-dev 
package. Why should developers HAVE to build the libraries from scratch?
- Make nuget package for windows folks... when we official support windows
- Make jar for maven and eclipse systems

These (plus make install) have been on my list since Nov 2014.

Plus, a couple of comments inline.

Pat

> -----Original Message-----
> From: Rees, Kevron [mailto:kevron.m.rees at intel.com]
> Sent: Thursday, June 11, 2015 10:54 AM
> To: Lankswert, Patrick
> Cc: Schulhof, Gabriel; iotivity-dev at lists.iotivity.org
> Subject: Re: [dev] HashTag: FixMe
> 
> On Thu, Jun 11, 2015 at 7:17 AM, Lankswert, Patrick
> <patrick.lankswert at intel.com> wrote:
> > 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.
> 
> ironically, this breaks breaks our build machines when building iotivity for
> yocto which cannot download during compilation.

However, it should allow you to manually pull the tarball to the right place 
and skip the download.

> > - Folks would fail to download dependencies and could not determine
> > what was missing
> 
> It's pretty clear via the scons output when cereal is missing.  The output 
> even
> tells you the exact commands to clone a specific revision.
> This is also documented via the Readme.scons.txt.  This pattern could work
> for other dependencies.
> 
> > - Folks would download dependencies to the wrong directory
> 
> using pkgconfig on linux would help here.  i don't know how to solve this on
> windows.
> 
> > - Folks would download the wrong version of the dependencies and
> > report issues as bugs
> >
> 
> maybe this is a scons limitation, but other build systems (such as
> cmake) can fail at configure if you don't have the specified version of a
> package.
> 
> > Regarding unit tests; is 'TEST=0' currently a build option?
> >
> 
> it may not be an official build option.  scons only checks if TEST == '1'.  
> Setting
> it to 'monkeys' will have the same effect as '0'.
> 
> > Regarding a 'make install' equivalent; I agree. Are you recommending the
> use of your install script?
> >
> 
> I recommend cmake :)

This was hashed out a long time ago. There was a negative for cmake, but I 
forget what the issue was. Some of the requirements for build systems when not 
building on linux were pretty bad.

> Also, one more wish I should include is that the arduino support be built into
> a proper arduino library.  There's no reason why scons needs to use the
> arduino IDE to build things.  'make install' might also solve this problem.
> 
> > 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

Reply via email to