Re: lablgtk, camlimages, advi, cameleon and libpng.

[Maxence Guesdon <maxence.guesdon@inria.fr>]

On Thu, 8 Jan 2004 17:17:52 +0100
Sven Luther <sven.luther@wanadoo.fr> wrote:

> Hello,
> 
> Well, we encountered a build problem in advi, which seems to be related
> to cameleon's linkage of libpng10 and lablgtk.
> 
> I don't remember what the situation is exactly, but i remember that
> libpng10 was to be used with lablgtk1, and libpng12 was to be used with
> lablgtk2 and that cameleon is the only remaining app that depends on
> lablgtk2.

Heu, cameleon (the main trunk) depends on lablgtk1, not lablgtk2.

> I thus propose the following plan, and an alternative plan below it :
> 
> Plan A:
> 
>   - we rename lablgtk2 to lablgtk, and it becomes our default lablgtk.
>   - lablgtk2 is linked with libpng12.
>   - camlimage is built with it.
>   - we rename current lablgtk as lablgtk1 for compatibility reasons.
>   - cameleon is either fixed to build with lablgtk2.
> 
> Plan B:
> 
>   - we upload a camlimage2 linked with libpng12 and using lablgtk2.
>   - cameleon is linked with camlimage1 and lablgtk1 and libpng10.
>   - advi is linked with camlimage2.
> 
> What do you think of it ? Especially, i would like comments from the
> cameleon people, but it has been a long time since the lablgtk2
> migration was started, so ...

And it is not done, yet. It is started in a separated branch, named ...
"lablgtk2" :-)

Friendly,

Maxence