kicad-developers team mailing list archive

[Manveru <manveru@...>]

--0016364d30ef7d0ed90474b13b55 Content-Type: text/plain; charset=UTF-8

2009/9/28 Alain Mouette <alainm@...>

>
>
>
> Dick Hollenbeck escreveu:
>
> >
> > You make some good points. But on balance the convenience to Windows
> > users and to those who have packages older than what we require in their
> > linux distribution weighs greater than other concerns IMO.
>
> Thanks very much for that idea (and the willingness to implement it...)
>
> I just couls add, that kicad uses just a very limited set of functions
> of boost. If no problems arise in that specific use of those specific
> functions, kicad can go on using a single version of boost *forever*...
> Only to be updated by kicad team if/when needed :)
>
> Alain
>
> 
>

My two cents: And this is corporate model of many libraries included in
project and then statically linked into application. This protects team from
changes in API in new library version or in functionality during project
development. Alignment to new libraries is done at last stage before release
(or not - if there is such decision from project management).

Putting boost headers in the project tree is quite popular in open source
projects (LyX do this).
-- 
Manveru
jabber: manveru@...
gg: 1624001
http://www.manveru.pl
 --0016364d30ef7d0ed90474b13b55 Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2009/9/28 Alain Mouette <span dir=3D"ltr=
">&lt;<a href=3D"mailto:alainm@...";>alainm@...</a>&gt;</span><b=
r><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204=
, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">











<div style=3D"background-color: rgb(255, 255, 255);">
<span>=C2=A0</span>

<div style=3D"width: 655px;">
<div style=3D"margin: 0pt; padding: 0pt 25px 0pt 0pt; width: 470px; float: =
left;">

<div>
<p><br>
Dick Hollenbeck escreveu:</p><div class=3D"im"><br>
&gt; <br>
&gt; You make some good points. But on balance the convenience to Windows =
<br>
&gt; users and to those who have packages older than what we require in the=
ir <br>
&gt; linux distribution weighs greater than other concerns IMO. <br>
<br></div>
Thanks very much for that idea (and the willingness to implement it...)<br>
<br>
I just couls add, that kicad uses just a very limited set of functions <br>
of boost. If no problems arise in that specific use of those specific <br>
functions, kicad can go on using a single version of boost *forever*... <br=
>
Only to be updated by kicad team if/when needed :)<br>
<br>
Alain<br>
<br>

=20

</div>=20=20

=20=20=20=20
<div width=3D"1" style=3D"color: white; clear: both;"></div>

=20=20=20=20=20=20=20=20=20=20=20
=20=20
=20=20=20=20
=20=20=20=20
</div></div></div>
=09
=09


=09


=09
=09
=09
=09
=09

</blockquote></div><br><br clear=3D"all">My two cents: And this is corporat=
e model of many libraries included in project and then statically linked in=
to application. This protects team from changes in API in new library versi=
on or in functionality during project development. Alignment to new librari=
es is done at last stage before release (or not - if there is such decision=
from project management).<br>
<br>Putting boost headers in the project tree is quite popular in open sour=
ce projects (LyX do this).<br>-- <br>Manveru<br>jabber: manveru@...<=
br> =C2=A0 =C2=A0 gg: 1624001<br> =C2=A0 <a href=3D"http://www.manveru.pl";>=
http://www.manveru.pl</a><br>

 --0016364d30ef7d0ed90474b13b55--