Subject: [ggl] Re: problems with Boost Geometry Xcode compile?
From: Barend Gehrels (Barend.Gehrels)
Date: 2010-03-10 09:06:44
> When I write a C++ program, I always include stuff in the following
> order: C standard lib, C++ standard lib, boost headers, other 3rd
> party headers, my headers. Boost users should be advised to do this
> way (I remember that Boost.Python has the same constraint in some
> contexts) and that will easily avoid the majority of possible
Indeed, this is how it is also recommended for Boost.Geometry
internally, and we can write it in the Compiling chapter. So yes, I do
agree with this.
Mark, does this solve your problem (without need to undef)?
Geometry list run by mateusz at loskot.net