Boost logo

Geometry :

Subject: Re: [geometry] type based tag dispatching for VTK output
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2013-06-07 09:53:23

On 7 June 2013 14:27, Tomislav Maric <tomislav.maric_at_[hidden]> wrote:
> On 06/07/2013 10:51 AM, Mateusz Loskot wrote:
>> On 7 June 2013 09:05, Tomislav Maric <tomislav.maric_at_[hidden]> wrote:
>>> On 06/07/2013 12:20 AM, Barend Gehrels wrote:
>> If I may, I'd suggest to restructure the repository tree to include full path to
>> the headers, as it is a common practice in external additions for Boost.
>> It means, once the repo is cloned, it would be good to have:
>> /boost/geometry/extensions/io/vtk
>> /libs/geometry/extensions/test/io/vtk
>> This makes it much easier to integrate your work with Boost sources tree,
> Thank you for the tip, it's done + the repo is updated. All the test
> apps are installed in build/bin now as well. I'm sticking with cmake for
> now, later the include directives need to be changed to account for
> linux FHS directories </boost/geometry/..> but there is much more to do
> before that becomes necessary.

I sense misunderstanding, the paths
are not meant to denote Unix paths, but / means repository root.
IOW, it should be read as


Certainly, Boost header are never included with
#include </boost/...>
but just
#include <boost/...>

The point I was trying to make is to keep structure of repository of
third-party extensions
for Boost to be exactly the same as original structure of Boost SVN trunk:

This is common practice in Boost Sandbox with misc proposals and extensions:

So, users can do something along these lines:

svn co mycopy
cp -a {GIT_REPO_ROO}/boost mycopy/boost
cp -a {GIT_REPO_ROO}/libs mycopy/libs

Anyway, just a loose suggestion.

Best regards,

Mateusz Loskot,

Geometry list run by mateusz at