<div dir="ltr">hi, <div><br></div><div style>thanks for the feedback, </div><div style><br></div><div style>I thought it was dynamically linked</div><div style>I tested it on a Mac OS 10.6.6 32bit machine where I installed OpenCV 2.3.3 with Fink</div>
<div style>and it works well</div><div style><br></div><div style>should I embbed the library in the mach-o ?</div><div style>if so, I don't how to...</div><div style><br></div><div style>but actually I made few changes after the build I've tested and before uploading so maybe I broke something...<br>
</div><div style><br></div><div style>I will give it a try tomorow</div><div style><br></div><div style>cheers</div><div style><br></div><div style>a</div></div><div class="gmail_extra"><br clear="all"><div>--<br>do it yourself <br>
<a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br></div>
<br><br><div class="gmail_quote">2013/2/7 me.grimm <span dir="ltr"><<a href="mailto:megrimm@gmail.com" target="_blank">megrimm@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
hey antoine<br>
<br>
i just tried your build and it didnt work. i get:<br>
<br>
/Users/megrimm/Desktop/pix_opencv/pix_opencv_athreshold.pd_darwin:<br>
dlopen(/Users/megrimm/Desktop/pix_opencv/pix_opencv_athreshold.pd_darwin,<br>
10): Library not loaded: /sw/lib/libopencv_core.2.3.dylib<br>
Referenced from:<br>
/Users/megrimm/Desktop/pix_opencv/pix_opencv_athreshold.pd_darwin<br>
Reason: no suitable image found. Did find:<br>
/sw/lib/libopencv_core.2.3.dylib: mach-o, but wrong architecture<br>
/usr/local/lib/libopencv_core.2.3.dylib: mach-o, but wrong architecture<br>
<br>
because your dylibs are not embeded in the folder (mach-o, but wrong<br>
architecture errors are from my 64bit builds)<br>
<div class="im"><br>
>> >> ./embed-MacOSX-dependencies.sh finds all the dynamic libraries needed<br>
>> >> and embeds them in the folder. Then you can tarbz the whole pix_opencv<br>
>> >> folder, and that's the installable library. Just drop that into<br>
>> >> ~/Library/Pd or /Library/Pd.<br>
<br>
</div>so this didnt seem to work?<br>
<br>
m<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Thu, Jan 31, 2013 at 11:49 AM, Antoine Villeret<br>
<<a href="mailto:antoine.villeret@gmail.com">antoine.villeret@gmail.com</a>> wrote:<br>
> hi,<br>
><br>
> so i made a folder called "antoine" in the home of pddev on macosx105-i386<br>
> i build pix_opencv against latest Gem and pd vanilla 0.44<br>
> it doesn't compile with pd-extended (sorry for that)<br>
><br>
> i've made a tarball of the folder and put it here :<br>
> <a href="http://puredata.info/Members/avilleret/pix_opencv_macosx_20130131/view" target="_blank">http://puredata.info/Members/avilleret/pix_opencv_macosx_20130131/view</a><br>
> how can i put it on the pix_opencv page ?<br>
><br>
> cheers<br>
><br>
> antoine<br>
><br>
><br>
> --<br>
> do it yourself<br>
> <a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br>
><br>
><br>
> 2013/1/3 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>><br>
>><br>
>><br>
>> On 01/03/2013 03:10 PM, Antoine Villeret wrote:<br>
>> > Hi Hans and all,<br>
>> ><br>
>> > happy new year and thanks for your work<br>
>> ><br>
>> > sorry for the delayed answer, I was far away from Internet in the<br>
>> > mountain for few days...<br>
>><br>
>> Definitely don't apologize for that, I wish I had been in the mountains :)<br>
>><br>
>> > I can log through SSH on pdlab computers (not tested all for now) but I<br>
>> > have few more questions :<br>
>> ><br>
>> > 1- What can I do and (more important) what should I never do on those<br>
>> > machines (particularly about SVN checkout and installing / updating lib)<br>
>><br>
>> The pddev is pretty locked down, so I think you'd have to try to mess<br>
>> things<br>
>> up bad. The biggest worry would be filling up the disks on some of the<br>
>> VMs,<br>
>> since they are only 9 gigs. I think the Macs all have lots of disk.<br>
>><br>
>> > 2- There is no "pix_opencv" folder in the pddev home (on<br>
>> > <a href="http://macosx105-i386.pdlab.puredata.info" target="_blank">macosx105-i386.pdlab.puredata.info</a>) where could I find the up-to-date<br>
>> > folder ? should I cd to<br>
>> > /Users/pddev/pure-data/trunk/externals/pix_opencv (this seems to be very<br>
>> > old) ?<br>
>> > Where should I work ?<br>
>><br>
>> Work wherever you'd like. I generally put svn checkouts in ~/code, use<br>
>> that,<br>
>> or ~/pure-data, or create your own folder if you want. I think the<br>
>> biggest<br>
>> rule would be don't mess with or delete files there that you didn't<br>
>> create.<br>
>><br>
>><br>
>> > sorry for those silly questions, but i don't want to break something...<br>
>><br>
>> Thanks for asking!<br>
>><br>
>><br>
>> ><br>
>> > a.<br>
>> ><br>
>> > PS : this message should be signed with OpenPGP :-)<br>
>><br>
>> Yup, its verified. :)<br>
>><br>
>> hc<br>
>><br>
>><br>
>> ><br>
>> > Le 31/12/2012 18:28, Hans-Christoph Steiner a écrit :<br>
>> >><br>
>> >> Hey Antoine,<br>
>> >><br>
>> >> So I installed OpenCV 2.3.1 on the PdLab Macs using Fink, and fixed the<br>
>> >> Makefile to use pkg-config on all platforms. I don't know the protocol on<br>
>> >> editing the README, so I didn't touch it. It would make things easier for<br>
>> >> users if there was only one build system and the README only covered that.<br>
>> >> I'll leave that to you. Here's how to make a build on Mac OS X:<br>
>> >><br>
>> >> $ . /sw/bin/init.sh (load Fink for other libs like opencv)<br>
>> >> $ cd pix_opencv<br>
>> >> $ make<br>
>> >> PD_PATH=/Users/pd/auto-build/pd-extended/packages/darwin_app/build/Pd-0.43.4-extended-20121231.app/Contents/Resources/<br>
>> >> $ ./embed-MacOSX-dependencies.sh .<br>
>> >><br>
>> >> ./embed-MacOSX-dependencies.sh finds all the dynamic libraries needed<br>
>> >> and embeds them in the folder. Then you can tarbz the whole pix_opencv<br>
>> >> folder, and that's the installable library. Just drop that into<br>
>> >> ~/Library/Pd or /Library/Pd.<br>
>> >><br>
>> >> For the PdLab Macs, building on <a href="http://macosx105-i386.pdlab.puredata.info" target="_blank">macosx105-i386.pdlab.puredata.info</a> will<br>
>> >> include the 32-bit libraries, which is what you need for current versions of<br>
>> >> Pd-extended for Mac OS X. Gem included in Pd-extended doesn't work for<br>
>> >> 64-bit (Gem master does at this point, I think). Building on<br>
>> >> macosx106-x86_64 (<a href="http://chaos.medien.uni-weimar.de" target="_blank">chaos.medien.uni-weimar.de</a>) will make 64-bit builds.<br>
>> >><br>
>> >> For someone to build this on their own machine, they'll need to do:<br>
>> >><br>
>> >> fink install opencv-dev<br>
>> >><br>
>> >> On a related note, if you stick with the Library Template Makefile and<br>
>> >> layout, that it'll be trivially easy to make Debian packages for it. I can<br>
>> >> do that too, or leave it to you.<br>
>> >><br>
>> >> .hc<br>
>> >><br>
>> >><br>
>> >> On Dec 27, 2012, at 3:36 PM, Hans-Christoph Steiner wrote:<br>
>> >><br>
>> >>><br>
>> >>> Hey Antoine,<br>
>> >>><br>
>> >>> If you are willing to maintain Mac OS X and/or Windows ports, you can<br>
>> >>> get access to the PdLab build machines, and I'm willing to install opencv<br>
>> >>> 2.4.x on those machines. Basically, once everything is setup, you'll just<br>
>> >>> need to make the builds on the various platforms by doing 'make'.<br>
>> >>><br>
>> >>> .hc<br>
>> >>><br>
>> >>> On Dec 27, 2012, at 10:35 AM, Antoine Villeret wrote:<br>
>> >>><br>
>> >>>> no idea, there wasn't any official opencv framework in the past, only<br>
>> >>>> some make by people who needs it but never maintained nor updated...<br>
>> >>>> so I think it still the case...<br>
>> >>>> people have to wait for someone who wants to make a framework, or to<br>
>> >>>> build it themselves<br>
>> >>>> but, are the packages available for Mac OS X through a package<br>
>> >>>> manager<br>
>> >>>> with automatic installation like in Debian ?<br>
>> >>>> if no, people have to build package by hand if I understood correctly<br>
>> >>>> so if they can build a pd package it will be very easy for them to<br>
>> >>>> build OpenCV 2 from lastest release<br>
>> >>>> which is I think a better idea than using an old and obsolete OpenCV<br>
>> >>>> Framework...<br>
>> >>>><br>
>> >>>> I don't have a Mac OS X machine under hand for now to test it<br>
>> >>>> but I think it's not really hard to make a step by step tutorial to<br>
>> >>>> make pix_opencv working on OS X with a tarball and some dev tool<br>
>> >>>><br>
>> >>>> --<br>
>> >>>> do it yourself<br>
>> >>>> <a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br>
>> >>>><br>
>> >>>><br>
>> >>>> 2012/12/27 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>:<br>
>> >>>>><br>
>> >>>>> Ah ok, makes sense. What about opencv2 on Mac OS X? How is that<br>
>> >>>>> handled?<br>
>> >>>>><br>
>> >>>>> .hc<br>
>> >>>>><br>
>> >>>>> On Dec 27, 2012, at 10:03 AM, Antoine Villeret wrote:<br>
>> >>>>><br>
>> >>>>>> the default make install command from git repo install gem into<br>
>> >>>>>> /usr/local/include<br>
>> >>>>>> --<br>
>> >>>>>> do it yourself<br>
>> >>>>>> <a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> 2012/12/27 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>:<br>
>> >>>>>>><br>
>> >>>>>>> What installs the headers into /usr/local/include/Gem? The Gem<br>
>> >>>>>>> package in Debian/Ubuntu installs into /usr/include/Gem, so<br>
>> >>>>>>> -I/usr/include/Gem needs to be there. If some standard installer installs<br>
>> >>>>>>> into /usr/local/include/Gem, then I'd keep -I /usr/local/include/Gem in<br>
>> >>>>>>> CFLAGS_linux, otherwise I'd leave it to people to edit the Makefile to add<br>
>> >>>>>>> their custom Gem header install locations.<br>
>> >>>>>>><br>
>> >>>>>>> .hc<br>
>> >>>>>>><br>
>> >>>>>>> On Dec 27, 2012, at 9:30 AM, Antoine Villeret wrote:<br>
>> >>>>>>><br>
>> >>>>>>>> hi,<br>
>> >>>>>>>><br>
>> >>>>>>>> thansk for that,<br>
>> >>>>>>>><br>
>> >>>>>>>> i had to change the CLAGS_linux variable (line 39) to :<br>
>> >>>>>>>> CFLAGS_linux = -I/usr/local/include/Gem `pkg-config --cflags<br>
>> >>>>>>>> opencv`<br>
>> >>>>>>>><br>
>> >>>>>>>> to make it<br>
>> >>>>>>>> but I don't know if I should or not push it to the SVN ?<br>
>> >>>>>>>><br>
>> >>>>>>>> --<br>
>> >>>>>>>> do it yourself<br>
>> >>>>>>>> <a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br>
>> >>>>>>>><br>
>> >>>>>>>><br>
>> >>>>>>>> 2012/12/27 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>:<br>
>> >>>>>>>>><br>
>> >>>>>>>>> Ok, I committed a Makefile based on the Library Template. It<br>
>> >>>>>>>>> does not build pix_opencv_contours.cc pix_opencv_matchshape.cc, they both<br>
>> >>>>>>>>> gave a big dump of roughly the same errors.<br>
>> >>>>>>>>><br>
>> >>>>>>>>> The template Makefile will handle a lot of things automatically<br>
>> >>>>>>>>> for you, the trade-off is that its strict about certain things: every object<br>
>> >>>>>>>>> must have a help patch, all example files must go into examples/, etc. The<br>
>> >>>>>>>>> template Makefile is really easy to make a Debian package from too.<br>
>> >>>>>>>><br>
>> >>>>>>>> really easy why not, but how ?<br>
>> >>>>>>>> if I should make it myself I need a little more help...<br>
>> >>>>>>>> the links on the page :<br>
>> >>>>>>>> <a href="http://puredata.info/dev/DebianPackagingStructure" target="_blank">http://puredata.info/dev/DebianPackagingStructure</a><br>
>> >>>>>>>> are not broken but doesn't point to the right discussion...<br>
>> >>>>>>>> anyway, I found the discussion and others but can't find anywhere<br>
>> >>>>>>>> a<br>
>> >>>>>>>> good step by step howto build debian package<br>
>> >>>>>>>> sorry, this will be my first debian package :-)<br>
>> >>>>>>>><br>
>> >>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> * is pix_opencv_opticalflow.pd an example or an abstraction? If<br>
>> >>>>>>>>> its an example, it should go into examples/ with of.frag. If its an<br>
>> >>>>>>>>> abstraction, it should have a help patch. Or if its just a text patch, it<br>
>> >>>>>>>>> can be left out of the Makefile and left as is.<br>
>> >>>>>>>><br>
>> >>>>>>>> I forgot this one...<br>
>> >>>>>>>> I placed it in the examples/ folder for now<br>
>> >>>>>>>> but working on optical flow externals is in my todo list (with<br>
>> >>>>>>>> gpu and opencl)<br>
>> >>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> * pix_opencv_blobtrack.cc seems to require opencv2, does that<br>
>> >>>>>>>>> mean both opencv 1.2 and opencv 2.x need to be installed? Is there an<br>
>> >>>>>>>>> OpenCV2 framework for Mac OS X?<br>
>> >>>>>>>><br>
>> >>>>>>>> yes, most of recent and future externals take advantages of the<br>
>> >>>>>>>> new<br>
>> >>>>>>>> C++ API of OpenCV 2.x<br>
>> >>>>>>>> OpenCV 2 releases are distribute as a tarball for Linux/OSX,<br>
>> >>>>>>>> there is<br>
>> >>>>>>>> no Framework on the download page<br>
>> >>>>>>>> <a href="http://opencv.org/downloads.html" target="_blank">http://opencv.org/downloads.html</a><br>
>> >>>>>>>> and a quick search lead to multiple posts over the internet on<br>
>> >>>>>>>> how to<br>
>> >>>>>>>> build it by hand (which very easy since the new cmake system)<br>
>> >>>>>>>> and also a precompiled package :<br>
>> >>>>>>>> <a href="http://vislab.cs.vt.edu/~vislab/wiki/images/4/44/OpenCV2.0.dmg" target="_blank">http://vislab.cs.vt.edu/~vislab/wiki/images/4/44/OpenCV2.0.dmg</a><br>
>> >>>>>>>> found here :<br>
>> >>>>>>>> <a href="http://opencv.willowgarage.com/wiki/Mac_OS_X_OpenCV_Port" target="_blank">http://opencv.willowgarage.com/wiki/Mac_OS_X_OpenCV_Port</a><br>
>> >>>>>>>> but it's obsolete<br>
>> >>>>>>>><br>
>> >>>>>>>> ++<br>
>> >>>>>>>> a<br>
>> >>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>>>> On Mac OS X, I was building against Pd-extended 0.43 since<br>
>> >>>>>>>>> pix_opencv uses some new Gem headers that aren't included in Pd-extended<br>
>> >>>>>>>>> 0.42. The template Makefile automatically looks in Pd-extended if its in<br>
>> >>>>>>>>> /Applications. If you want to choose which version of Pd-extende to build<br>
>> >>>>>>>>> against:<br>
>> >>>>>>>>><br>
>> >>>>>>>>> make<br>
>> >>>>>>>>> PD_PATH=/Applications/Pd-0.43.4-extended-20121223.app/Contents/Resource<br>
>> >>>>>>>>><br>
>> >>>>>>>>> .hc<br>
>> >>>>>>>>><br>
>> >>>>>>>>> On Dec 26, 2012, at 3:11 PM, Antoine Villeret wrote:<br>
>> >>>>>>>>><br>
>> >>>>>>>>>> hello,<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> I made an update today on pix_opencv with an improvement of<br>
>> >>>>>>>>>> pix_opencv_contours which is now a complete replacement of<br>
>> >>>>>>>>>> other<br>
>> >>>>>>>>>> pix_opencv_contours_* objects<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> and I sent a private mail to Lluis even if I found some old<br>
>> >>>>>>>>>> mails on<br>
>> >>>>>>>>>> this list by him and i never get any answer<br>
>> >>>>>>>>>> so maybe you can go ahead according to the "one week consensus"<br>
>> >>>>>>>>>> ?<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> there is actually one strange make rule, its for a custom<br>
>> >>>>>>>>>> blobtracker<br>
>> >>>>>>>>>> but I will change this as soon as i have time<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> merry chrismas to all<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> cheers<br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> a<br>
>> >>>>>>>>>> --<br>
>> >>>>>>>>>> do it yourself<br>
>> >>>>>>>>>> <a href="http://antoine.villeret.free.fr" target="_blank">http://antoine.villeret.free.fr</a><br>
>> >>>>>>>>>><br>
>> >>>>>>>>>><br>
>> >>>>>>>>>> 2012/12/13 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>:<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> On Dec 13, 2012, at 12:21 PM, Antoine Villeret wrote:<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>>> 2012/12/13 Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>>:<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> On Dec 13, 2012, at 3:43 AM, IOhannes m zmoelnig wrote:<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----<br>
>> >>>>>>>>>>>>>> Hash: SHA1<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> On 2012-12-12 19:42, Antoine Villeret wrote:<br>
>> >>>>>>>>>>>>>>> i've already tried to make a C++ external from the<br>
>> >>>>>>>>>>>>>>> template but i<br>
>> >>>>>>>>>>>>>>> never reach something which works so if you have a working<br>
>> >>>>>>>>>>>>>>> template<br>
>> >>>>>>>>>>>>>>> please let me know<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> pix-opencv depends on external libraries, and afaik often<br>
>> >>>>>>>>>>>>>> needs<br>
>> >>>>>>>>>>>>>> specific versions thereof.<br>
>> >>>>>>>>>>>>>> i think it is a perfect candidate to *not* use a template<br>
>> >>>>>>>>>>>>>> Makefile but<br>
>> >>>>>>>>>>>>>> instead use something more intelligent like autotools,<br>
>> >>>>>>>>>>>>>> scons,<br>
>> >>>>>>>>>>>>>> cmake,...which reminds me that it already does use autoconf<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>>> and what about including it in Gem ? as it depends on it<br>
>> >>>>>>>>>>>>>>> (and it<br>
>> >>>>>>>>>>>>>>> may depends on very new feature such as ROI soon) i think<br>
>> >>>>>>>>>>>>>>> it's a<br>
>> >>>>>>>>>>>>>>> better choice<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> pix-opencv is developed by different people than Gem. i<br>
>> >>>>>>>>>>>>>> think it is<br>
>> >>>>>>>>>>>>>> good to keep the repositories (and user-management)<br>
>> >>>>>>>>>>>>>> separate.<br>
>> >>>>>>>>>>>>>> so: i'd rather not have pix-opencv be "part" of Gem.<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> but:<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> i agree that pix-opencv could be made more readily<br>
>> >>>>>>>>>>>>>> available to users.<br>
>> >>>>>>>>>>>>>> it might be a good idea to distribute it together with<br>
>> >>>>>>>>>>>>>> Gem-releases.<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> so:<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> the build-system needs little changes to build a pix_opencv<br>
>> >>>>>>>>>>>>>> found in<br>
>> >>>>>>>>>>>>>> extra/ (basically, uncomment the relevant lines at the end<br>
>> >>>>>>>>>>>>>> of<br>
>> >>>>>>>>>>>>>> extra/<a href="http://configure.ac" target="_blank">configure.ac</a> and add a line to extra/Makefile.am)<br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>><br>
>> >>>>>>>>>>>>>> we could then create a script that pulls in pix-opencv to<br>
>> >>>>>>>>>>>>>> extra/pix_opencv before the builds are actually started.<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> autotools are very useful for detecting platform differences<br>
>> >>>>>>>>>>>>> and making the build system respond differently based on that, like handling<br>
>> >>>>>>>>>>>>> multiple optional dependencies like in Gem. For the case you describe, that<br>
>> >>>>>>>>>>>>> works well with the template Makefile. For an object that requires a<br>
>> >>>>>>>>>>>>> specific library, add it to LDFLAGS. If that library not installed, it'll<br>
>> >>>>>>>>>>>>> throw an error, which is what you want since the object requires that<br>
>> >>>>>>>>>>>>> library. pix_opencv requires opencv, and does nothing without it, so no<br>
>> >>>>>>>>>>>>> autotools necessary.<br>
>> >>>>>>>>>>>><br>
>> >>>>>>>>>>>> I don't know anything about autotool and it looks like quite<br>
>> >>>>>>>>>>>> dark for<br>
>> >>>>>>>>>>>> me so if i can avoid another headache it's better :-)<br>
>> >>>>>>>>>>>><br>
>> >>>>>>>>>>>><br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> As for version differences, I generally find it way too much<br>
>> >>>>>>>>>>>>> work to support building against various versions of the API and just choose<br>
>> >>>>>>>>>>>>> one and standardize on it. Then, once this lib is widely distributed it<br>
>> >>>>>>>>>>>>> could be worth building against different versions of opencv if there is<br>
>> >>>>>>>>>>>>> demand. First get it out there for the majority of users, then deal with<br>
>> >>>>>>>>>>>>> any relevant edge cases, otherwise you are likely to spend lots of time<br>
>> >>>>>>>>>>>>> dealing with edge cases that might not really be relevant.<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> My problem with autotools is that very few people know how<br>
>> >>>>>>>>>>>>> to modify it, so the build system then rots because its not maintained and<br>
>> >>>>>>>>>>>>> other issues. I've seen this happen to a lot of autotools build systems in<br>
>> >>>>>>>>>>>>> Pd projects over the years. For example, Gem's autotools setup has gotten<br>
>> >>>>>>>>>>>>> so complex, its almost impenetrable for me, and I've done a fair amount of<br>
>> >>>>>>>>>>>>> autotools. This is one reason to not include every object in Gem.<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> The Makefile that's there is already quite close to working.<br>
>> >>>>>>>>>>>>> I'm happy to commit fixes to get it working if that's OK with the<br>
>> >>>>>>>>>>>>> maintainers. I've committed to pix_opencv before. Indeed I did this work<br>
>> >>>>>>>>>>>>> back in 2009 but sevy objected so it was reverted and abandoned:<br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>><br>
>> >>>>>>>>>>>>> <a href="http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/pix_opencv/Makefile?r1=12563&r2=12571" target="_blank">http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/pix_opencv/Makefile?r1=12563&r2=12571</a><br>
>> >>>>>>>>>>>><br>
>> >>>>>>>>>>>> I think we should ask Lluis for that<br>
>> >>>>>>>>>>>> with the current Makefile in the SVN man should have opencv<br>
>> >>>>>>>>>>>> >= 2.3<br>
>> >>>>>>>>>>>> (some externals won't compile with previous OpenCV version)<br>
>> >>>>>>>>>>>> but there<br>
>> >>>>>>>>>>>> is not check about that I think<br>
>> >>>>>>>>>>>> and I can build with<br>
>> >>>>>>>>>>>> ./configure --with-pd=<PATH> --with-gem=<PATH><br>
>> >>>>>>>>>>>> make<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> The Makefile equivalent of this is:<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> make PD_SRC=<PATH> GEM_SRC=<PATH><br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> Otherwise it'll look in the default installed locations for<br>
>> >>>>>>>>>>> the headers.<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>>> but only tested on Ubuntu<br>
>> >>>>>>>>>>>> I don't know if it could build on other linux distro and even<br>
>> >>>>>>>>>>>> less on<br>
>> >>>>>>>>>>>> Mac OS X and Windows<br>
>> >>>>>>>>>>>> Should fixing that Makefile.in be a starting point to<br>
>> >>>>>>>>>>>> distrute the package ?<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> Let me know and i'll do it. Is Lluis on this list? Yes, I<br>
>> >>>>>>>>>>> can include 'make osx_tarball' so its easy to make the tarball for releases.<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>> .hc<br>
>> >>>>>>>>>>><br>
>> >>>>>>>>>>><br>
>> >>>>>>>>><br>
>> >>>>>>><br>
>> >>>>><br>
>> >>><br>
>> >><br>
>> ><br>
>><br>
><br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> GEM-dev mailing list<br>
> <a href="mailto:GEM-dev@iem.at">GEM-dev@iem.at</a><br>
> <a href="http://lists.puredata.info/listinfo/gem-dev" target="_blank">http://lists.puredata.info/listinfo/gem-dev</a><br>
><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
____________________<br>
m.e.grimm | m.f.a | ed.m.<br>
<a href="mailto:megrimm@gmail.com">megrimm@gmail.com</a><br>
_________________________________<br>
</font></span></blockquote></div><br></div>