Re: [matplotlib-devel] Directories for C/C++ extensions

On Mon, Oct 21, 2013 at 7:36 PM, Chris Barker wrote: > > To expand slightly, with the current situation the onus is on us to > ensure > > that mpl builds OK and passes all of our tests with and without each of > the > > external libraries. > > If you only have internal libs, then there is less to

Re: [matplotlib-devel] Directories for C/C++ extensions

On 21 October 2013 18:36, Chris Barker wrote: > > we can all be confident that it will work correctly. > > only if you've tested against the version (maybe patched) of the > external lib they are using... > Of course not. We provide the framework to build mpl and run tests. Distro developers c

Re: [matplotlib-devel] Directories for C/C++ extensions

> To expand slightly, with the current situation the onus is on us to ensure > that mpl builds OK and passes all of our tests with and without each of the > external libraries. If you only have internal libs, then there is less to do -- it only need to work with the version you bundle. And making

Re: [matplotlib-devel] Directories for C/C++ extensions

On 10/19/2013 04:14 AM, Ian Thomas wrote: On 18 October 2013 19:18, Chris Barker > wrote: Ian, > I am working on a PR to replace the use of matplotlib.delaunay with the > Qhull library. nice! -- ( though I sure wish Qhull did constrained delaun

Re: [matplotlib-devel] Directories for C/C++ extensions

On 18 October 2013 19:18, Chris Barker wrote: > Ian, > > > I am working on a PR to replace the use of matplotlib.delaunay with the > > Qhull library. > > nice! -- ( though I sure wish Qhull did constrained delaunay...) > > > Installation will be similar to the existing packages LibAgg > > and CXX

Re: [matplotlib-devel] Directories for C/C++ extensions

On Oct 18, 2013 8:20 PM, "Chris Barker" wrote: > > Ian, > > > I am working on a PR to replace the use of matplotlib.delaunay with the > > Qhull library. > > nice! -- ( though I sure wish Qhull did constrained delaunay...) > > > Installation will be similar to the existing packages LibAgg > > and C

Re: [matplotlib-devel] Directories for C/C++ extensions

Ian, > I am working on a PR to replace the use of matplotlib.delaunay with the > Qhull library. nice! -- ( though I sure wish Qhull did constrained delaunay...) > Installation will be similar to the existing packages LibAgg > and CXX in that if the system already has a sufficiently recent versio

Re: [matplotlib-devel] Directories for C/C++ extensions

On 7 October 2013 15:22, Michael Droettboom wrote: > I like this idea. I've seen this called "extern" in other projects, but I > don't have a strong feeling about the name. I think it's good idea for all > of the reasons you mention. > OK, 'extern' seems the best directory name. After I've fi

Re: [matplotlib-devel] Directories for C/C++ extensions

Sent: Sunday, October 06, 2013 4:09 PM To: matplotlib-devel@lists.sourceforge.net Subject: [matplotlib-devel] Directories for C/C++ extensions Fellow developers, I am working on a PR to replace the use of matplotlib.delaunay with the Qhull library. Installation will be similar to the existing pa

Re: [matplotlib-devel] Directories for C/C++ extensions

On 2013/10/06 10:09 AM, Ian Thomas wrote: > Fellow developers, > > I am working on a PR to replace the use of matplotlib.delaunay with the > Qhull library. Installation will be similar to the existing packages > LibAgg and CXX in that if the system already has a sufficiently recent > version of Qh

[matplotlib-devel] Directories for C/C++ extensions

Fellow developers, I am working on a PR to replace the use of matplotlib.delaunay with the Qhull library. Installation will be similar to the existing packages LibAgg and CXX in that if the system already has a sufficiently recent version of Qhull installed then matplotlib will use that, otherwis