Re: [Mlt-devel] pull from

[jb <j-...@us...>]

On Sunday 26 July 2009 11:17:16 jb wrote:
> On Sunday 26 July 2009 07:25:02 Dan Dennedy wrote:
> 
> > I think you both raise good points here, but I think the number of
> > people who want to render kdenlive projects on a system without
> > kdenlive is rather limited and advanced (e.g. requires common mount
> > points of network file systems or shared storage for media file
> > references). If you think this will be evolving quite a bit over the
> > next months or year, then I think it should go in kdenlive repo. Quite
> > likely a lot people who might want to use it outside of kdenlive may
> > be able to simply copy the binary module to the other mlt-only system.
> > So, I think we can wait to move it to mlt after it stabilizes and
> > perhaps after some amount of user requests.
> > 
> 
> Having worked a bit on the titler module, I think it still needs a lot of work to be stable and complete,
> so I really think it makes more sense to have it in Kdenlive. I will prepare the integration to Kdenlive's svn soon.

After trying to figure out how to build an MLT module with cmake (seems ok now), I am starting to see some trouble that could appear...

1) MLT has a rather complex config script to set different compilation flags & optimisations. It seems hard to reproduce it all with cmake and we can never be sure that users will use the exact same compile flags when compiling MLT and Kdenlive. Could that lead to a problem with mlt's modules compiled inside Kdenlive?

2) Currently, it looks like MLT can only load modules that are in his install prefix. For example:

MLT is installed in /usr/local.
It correctly finds modules in /usr/local/lib/mlt but not in /usr/lib/mlt or any other library path
of course you can set the MLT_REPOSITORY variable but only one directory is allowed for the modules.

So it means that kdenlive's MLT modules HAVE to be installed in the exact same directory as MLT's original modules which is not always convenient (for example if MLT is in /usr/local, you can't install Kdenlive as a normal user, you will need root access to install the MLT module)

3) Looks like importing the module from git to Kdenlive's svn will loose all history

I am a bit afraid that this will create an installation nightmare with mismatching libraries, etc...
Maybe the best would be to have the titler module in Kdenlive's svn only for the development period, but when we are ready to release a new Kdenlive version, we move the module to MLT?

Any idea on that matter?

jb