I'm not likely to use them in a project any time soon, but with this Mac OS X release, I can give them to my students who are playing with computer vision.
About stability, I mostly mean the API rather than crashing, etc.
.hc
On Oct 8, 2009, at 1:51 PM, ydegoyon@free.fr wrote:
after the one week workshop, i can say they are very stable, maybe still a few problems on OSX, as we don't test so much there, maybe you could help?
Hans-Christoph Steiner wrote:
How stable are the opencv objects? Do you think the API will still change? It would be nice to have them included in Pd-extended, but doing it too soon creates a lot of annoying work.
.hc
On Oct 6, 2009, at 11:57 AM, ydegoyon@free.fr wrote:
pdp_opencv and pix_opencv have the autotools working
Hans-Christoph Steiner wrote:
So far I've been working on an autotools build system for pd itself, not libraries. I haven't used autotools in libraries, so I don't really know what a template would look like. I guess pdvjtools would be a good library to test out those ideas.
.hc
On Oct 6, 2009, at 10:11 AM, dmotd wrote:
hans,
as an aside, what progress are you making on an automake template, do you have something that could be easily reapplied to various situations for pd libs?
there seem to be a few strategies, the iem builders (iem16/iemmatrix/zexy) for one, bryan jurish's moocow builders and a set made by tim blechmann (used with flext).
i still need to spend some time with the docs before i get into autotools propper. and any info would be useful.
cheers, dmotd
Programs should be written for people to read, and only incidentally for machines to execute.
- from Structure and Interpretation of Computer Programs
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman
Pd-dev mailing list Pd-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
----------------------------------------------------------------------------
Programs should be written for people to read, and only incidentally for machines to execute. - from Structure and Interpretation of Computer Programs