Status of devel/boost upgrade

[Dmitry Marakasov]

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 like bsd.boost.mk so porters
don't have to invent a bicycle and add custom check for boost, and users
don't run into conflicts.

Actually, it's going to be too little stuff there, so it may be
just included into port.mk, but I'd split it out for modularity.
The idea:

ports:
USE_BOOST=	yes|python

port.mk:
.if defined(USE_BOOST)
.include "${PORTSDIR}/Mk/bsd.boost.mk"
.endif

bsd.boost.mk:

.if defined(USE_BOOST) && ${USE_BOOST} == "python"
LIB_DEPENDS+=	boost_python:${PORTSDIR}/devel/boost-python
do-configure:	boost-check-python
.elif defined(USE_BOOST)
LIB_DEPENDS+=	boost_thread:${PORTSDIR}/devel/boost
.endif

boost-check-python:
.if !exists(${LOCALBASE}/include/boost/python.hpp)
	@${ECHO_MSG} "This port requires boost built with python support."
	@${ECHO_MSG} "Please uninstall boost and install boost-python."
	@${FALSE}
.endif

-- 
Dmitry Marakasov   .   55B5 0596 FF1E 8D84 5F56  9510 D35A 80DD F9D2 F77D
amdmi3 at amdmi3.ru  ..:  jabber: amdmi3 at jabber.ru    http://www.amdmi3.ru