kicad-developers team mailing list archive

[Cirilo Bernardo <cirilo_bernardo@xxxxxxxxx>]

----- Original Message -----

> From: Lorenzo Marcantonio <l.marcantonio@xxxxxxxxxxxx>
> To: Kicad Developers <kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Cc: 
> Sent: Wednesday, August 21, 2013 4:59 AM
> Subject: Re: [Kicad-developers] boost_root driven by https
> 
> On Tue, Aug 20, 2013 at 11:39:27AM -0500, Dick Hollenbeck wrote:
>>  batteries.  My current thinking is to try and use boost::async and forgo 
> use of other
>>  networking libraries on top of that.  On windows we will have to pick up 
> openssl support,
>>  and that may mean insisting on the python install to pull it from python 
> a-mingw-us.  I
>>  build it there, but not in DLL form yet.)
> 
> Uhmm... maybe I've lost something...
> 
> What do we need ssl for? the library sharing system?
> 
> Also, why do we need to pull in the whole boost stuff? Isn't already
> widely deployed as dependency?
> 
> -- 
> Lorenzo Marcantonio
> Logos Srl
> 


Hi Lorenzo,

 Although many *NIX developers' systems have boost installed there can be issues with the version number; it's safest to pull in a version which you know works.  I'd imagine even different Linux distributions also have their own way of deploying boost; Debian for example splits it into quite a few packages.  For MSWin, any version of boost can be installed anywhere. Pulling in the parts of boost used by KiCAD is a minor possible duplication of source code and it makes life so much easier for the developer.

 I'd imagine SSL is for the library sharing (github API demands it), but in reality I think it's a good idea to use SSL for many things.  It's been over 10 years since I've last worked on a network project in which clear data was acceptable. News sites may use data in the clear but as they move onto subscriptions they will push encrypted comms as well. SSL can also allow a large organization to share their own components via a remote server without exposing the information to the public.

- Cirilo