[GEM-dev] HALCON plugin

Jack jack at rybn.org
Thu Sep 30 15:26:22 CEST 2010


Very nice ! ;)
I hope it will work perfectly soon.
++

Jack



Le jeudi 30 septembre 2010 à 15:10 +0200, cyrille henry a écrit :
> ok, thanks for all the answer.
> i'm sorry, i was so exited to have it compiled, that i miss the end of the readme.
> 
> so, i'll not ask how to open a camera, since i now have read it till the end!
> 
> sending :
> device GigEVision::0030530f8e64  did not work, but :
> device GigEVision:default:0030530f8e64 did work.
> 
> so, i now have an image.
> well, i would be better if i had a lens on this camera ;-)
> 
> anyway, i noticed that some images are not correct.
> in attachment, you can find 2 examples of bad images...
> 
> 
> Cyrille
> 
> Le 30/09/2010 13:55, IOhannes m zmoelnig a écrit :
> > On 2010-09-30 13:17, cyrille henry wrote:
> >> Hello,
> >>
> >> i finally have an evaluation licence for the HALCON lib, for 1 month.
> >
> > cool.
> >
> >>
> >> i compile the halcon plug-in like explain in the readme.
> >> compilation was no problem.
> >> in Gem/src, i did a :
> >> ln -s plugins/*/.libs/*.so .
> >>
> >> so i've got 5 gem_video plug in :
> >> DC1394, DV4L, HALCON, V4L, V4L2
> >
> > not necessarily.
> > you have compiled 5 plugins, but some of them might not have enabled
> > their code.
> > e.g. if configure cannot find libdv, then you will end up with a bare
> > gem_videoDV4L.so, that basically does nothing....
> > anyhow
> >
> >>
> >>
> >> so, why did DV4L is not listed?
> >
> > see above.
> >
> >> is DC1394 replacing it?
> >
> > no, dc1394 uses idc (industrial video over ieee1394), wherase dv4l uses
> > IEC 61834 (aka: consumer a/v over ieee1394)
> >
> >>
> >> i try to cp libhalconcpp.so in diferents place, but i still have the
> >> same error.
> >> what sould i do so that gem_videoHALCON.so can load libhalconcpp.so?
> >
> > did you follow the steps in plugins/videoHALCON/README.txt that say:
> > <snip>
> > probably this won't work, with Gem complaining that it cannot find
> > "libhalconcpp.so" or similar.
> > in this case should tell the linker where to find the halcon-libraries,
> > using
> > the LD_LIBRARY_PATH variable:
> > $ LD_LIBRARY_PATH=${HALCONROOT}/lib/${HALCONARCH} pd -lib Gem
> > should do the trick.
> > </snip>
> >
> > mfgasdr
> > IOhannes
> >
> >
> >
> >
> > _______________________________________________
> > GEM-dev mailing list
> > GEM-dev at iem.at
> > http://lists.puredata.info/listinfo/gem-dev
> _______________________________________________
> GEM-dev mailing list
> GEM-dev at iem.at
> http://lists.puredata.info/listinfo/gem-dev





More information about the GEM-dev mailing list