[GEM-dev] [PD-dev] pix_opencv

[IOhannes m zmoelnig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2012-12-12 19:42, Antoine Villeret wrote:
> i've already tried to make a C++ external from the template but i 
> never reach something which works so if you have a working template
> please let me know

pix-opencv depends on external libraries, and afaik often needs
specific versions thereof.
i think it is a perfect candidate to *not* use a template Makefile but
instead use something more intelligent like autotools, scons,
cmake,...which reminds me that it already does use autoconf

> 
> and what about including it in Gem ? as it depends on it (and it
> may depends on very new feature such as ROI soon) i think it's a
> better choice

pix-opencv is developed by different people than Gem. i think it is
good to keep the repositories (and user-management) separate.
so: i'd rather not have pix-opencv be "part" of Gem.

but:

i agree that pix-opencv could be made more readily available to users.
it might be a good idea to distribute it together with Gem-releases.

so:

the build-system needs little changes to build a pix_opencv found in
extra/ (basically, uncomment the relevant lines at the end of
extra/configure.ac and add a line to extra/Makefile.am)



we could then create a script that pulls in pix-opencv to
extra/pix_opencv before the builds are actually started.

caveat:
both Gem and pix-opencv are complex projects. Gem has slow release
cycles, those of pix-opencv seems to be even more so.
synchronizing both projects so that we can create a "stable"
Gem-package including a "stable" pix-opencv could be impossible.

so in a way it would be better if pix-opencv was distributed
separately, but actively.



fgmasdr
Ihannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDJlRcACgkQkX2Xpv6ydvRQ0gCguxWsVlMU838wbLxW9zs0px4W
rmwAn2vf35asYl+NRTwxs+FXjtrWCzhk
=HCe3
-----END PGP SIGNATURE-----