matplotlib-devel Mailing List for matplotlib

Given the slow pace of development on PyCXX, I know it has been the 
desire of some here to remove our dependency on it.
I thought a helpful starting point to evaluate the alternatives would be 
to restructure one of our extensions to not use PyCXX anymore. I've 
taken the PNG extension, which is reasonably straightforward in that it 
doesn't define any custom types, but does have some low level C-wrapping 
challenges, and separated out the Python-specific parts from the 
libpng-specific parts. The Python-specific parts are now written using 
the "raw" Python C/API. The other part still uses C++ (not C) and does 
throw exceptions, but doesn't use classes or templates or anything else 
that can be difficult to wrap. All of this is on my "no_cxx" branch.
Now here's the challenge: can we do better than this using any of the 
available wrapping tools? Cython, SWIG, Boost.Python etc.? I've not had 
much luck with Cython for this kind of thing in the past, but I know it 
is popular. Perhaps someone with more Cython experience would want to 
take a crack at this and then we could have something concrete to compare...
Cheers,
Mike

Hi,
Yes, I am trying to build against custom-built libraries.
and thanks for the suggestion about LDFLAGS, but that didn't work too.
It still picks up system versions of the libraries.
What has pkg-config got to do with this? (I havent worked extensively with
linux so not much idea)
I think I should also mention that I am trying to build matplotlib against
Python 3.2.3.
Regards,
Tej
On Tue, Nov 27, 2012 at 10:49 PM, Michael Droettboom <md...@st...>wrote:
> You can try setting LDFLAGS to "-L/path/to/your/libraries".