Dmitry Marakasov píše v út 07. 04. 2009 v 20:13 +0400:
> * Alexander Churanov (alexanderchura...@gmail.com) wrote:
>
> > > We'll need an exp-run for it anyway, so I guess it's OK.
> > > If you have a patch ready, I suggest to file a PR and mail pav@ to do
> > > exp-run for it. If there are no majo
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
> > We'll need an exp-run for it anyway, so I guess it's OK.
> > If you have a patch ready, I suggest to file a PR and mail pav@ to do
> > exp-run for it. If there are no major failures, we can push it into the
> > tree, else we won't be bo
Dmitry,
> We'll need an exp-run for it anyway, so I guess it's OK.
> If you have a patch ready, I suggest to file a PR and mail pav@ to do
> exp-run for it. If there are no major failures, we can push it into the
> tree, else we won't be bored during the freeze fixing it.
As I understand this, it
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
> As I see everybody agrees on splitting boost into several ports and on
> Boost.Python beeing a separate port. Let's proceed with option #2
> ("jam", "libs", "python-libs" and "docs").
>
> Personally, I like the idea #4 of having source-l
OK, guys,
As I see everybody agrees on splitting boost into several ports and on
Boost.Python beeing a separate port. Let's proceed with option #2
("jam", "libs", "python-libs" and "docs").
Personally, I like the idea #4 of having source-libs and a port per a
shared library. I'd like to have anot
On Fri, 03 Apr 2009 09:50:11 -0600, Dmitry Marakasov
wrote:
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
There are 95 libraries in boost.
Woo, that's sure too many.
Let me explain that:
Boost has source-only libraries and separately-compiled libraries.
Source-only libraries
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
> There are 95 libraries in boost.
Woo, that's sure too many.
> Let me explain that:
> Boost has source-only libraries and separately-compiled libraries.
> Source-only libraries consist of header files only and do not require
> any compil
2009/4/3 Dmitry Marakasov :
> Not sure if splitting it into many small libraries is a good idea. How
> many are there, btw? Is it a port per libboost_*so, or per
> include/boost/* ?
Neither. Per the list of libraries: http://www.boost.org/doc/libs/1_38_0
There are 95 libraries in boost.
Those th
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
> I've already did it about a month ago. Currently I'm testing the
> solution. There are two ideas about splitting boost:
Woo, this is great!
> 1) Split it into bjam, source-libs, shared-libs, python-libs and docs.
> This is what was actu
2009/4/1 Dmitry Marakasov :
> * Jeremy Messenger (me...@cox.net) wrote:
>
>> No need bsd.boost.mk over that small stuff. How about resolve conflict for
>> real by split boost and boost-python by have boost only install non-python
>> stuff and boost-python install only python stuff?
>
> That of cour
* Jeremy Messenger (me...@cox.net) wrote:
> No need bsd.boost.mk over that small stuff. How about resolve conflict for
> real by split boost and boost-python by have boost only install non-python
> stuff and boost-python install only python stuff?
That of course would be harder and more interesti
On Tue, 31 Mar 2009 17:02:46 -0600, Dmitry Marakasov
wrote:
Hi!
By the way, I've just ran into this sample of code in www/openvrml:
.if exists(${LOCALBASE}/include/boost/python.hpp)
LIB_DEPENDS+= boost_python.4:${PORTSDIR}/devel/boost-python
.else
LIB_DEPENDS+= boost_regex.4:${PORTSDIR}/d
Hi!
By the way, I've just ran into this sample of code in www/openvrml:
.if exists(${LOCALBASE}/include/boost/python.hpp)
LIB_DEPENDS+= boost_python.4:${PORTSDIR}/devel/boost-python
.else
LIB_DEPENDS+= boost_regex.4:${PORTSDIR}/devel/boost
.endif
and thought: why don't we create something li
On Fri, 27 Mar 2009 09:29:19 -0600, Dmitry Marakasov
wrote:
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
As stated on http://wiki.freebsd.org/BoostPortingProject, all issues
with ports depending on devel/boost are resolved.
Thank guys for work on boost stuff.
Should I do some
* Alexander Churanov (alexanderchura...@gmail.com) wrote:
> As stated on http://wiki.freebsd.org/BoostPortingProject, all issues
> with ports depending on devel/boost are resolved.
> Should I do something for updating the port?
We're planning extra exp-run with all the fixes and patch to boost,
p
15 matches
Mail list logo
