Re: [Vxl-maintainers] ffmpeg and vxl

[Amitha P. <ami...@us...>]

Matt Leotta wrote:
> My only questions now is how current is
> "current"?  I could update and build FFMPEG as part of a nightly
> build.  I don't know how stable FFMPEG is on a daily basis and I don't
> want to propagate errors compiling FFMPEG to the VXL Dashboard.  But
> maybe it's stable enough to do that.

I don't think it's stable enough to track daily.

> Another option is that manually
> update the "current" version when it is stable and I see a reason to
> update it.  Thoughts on this?

This concept is what I have in mind.  As soon as there is a new feature 
or capability in a newer ffmpeg that does something I want, I'll update 
the "current" version in v3pbin/current.  All capabilities that are 
required in "current" will be captured by regression tests, so we can 
make sure that we aren't spoiling things for someone else.  (If it does 
break something for someone, they'd have to (help) write a regression 
test to capture their requirements.)

> This is exactly what I had in mind when I said separate repository.
> You can checkout vxl and not get v3pbin, but if you do checkout v3pbin
> into the vxl source directory an update of the vxl root will also
> update v3pbin.

I think this will work with some, but not all, cvs clients.  Even if it 
doesn't, all it involves is a second cvs update, and CMake can prompt 
you to do it.

Amitha.