To: patrick at watson.org
Cc: lablgtk at kaba.or.jp
Subject: Re: Improving lablgtk installation
In-Reply-To: <Pine.BSF.3.96.1010217145101.72507F-100000 at fledge.watson.org>
References: <Pine.BSF.3.96.1010217145101.72507F-100000 at fledge.watson.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010220103752P.garrigue at kurims.kyoto-u.ac.jp>
Date: Tue, 20 Feb 2001 10:37:52 +0900
From: Jacques Garrigue <garrigue at kurims.kyoto-u.ac.jp>
Lines: 36

> I think that making some minor modifications to the lablgtk installation
> could make the package more usable.

My impression is that the problem is not cause by lablgtk:

>   1) Install the .cmx files.  For users of 'ocamldep', the .cmx files
>      are generated as dependencies. I would also imagine this opens
>      up opportunities for inlining.

All the cmx are in lablgtk.cmxa, which should be all you need.

>   2) Build a native-code version of gtkThInit.ml

I'll think about this, but this file contains really a single line:
     let thread = GtkThread.start ()
It is only intended for toplevels.

>   3) Use 'cp -p' instead of regular 'cp' to preserve timestamps.
>      I usually have to 'touch' all the .cm[iox] files after
>      installation so that 'make' doesn't get confused.
>
>   4) Better support with OcamlMakefile. It's currently difficult to
>      use these init objects properly. They should be placed before all 
>      other .cmo files for order dependence reasons,
>      but it seems that only source files can show up in that location.

I think there is some confusion here: you should not have dependencies
on a library directory. If you want to add some, why not directly use
the source directory, which will have the expected behaviour.
 
>   5) Optional installation using 'findlib'.

Good suggestion. But I'll first have to learn how to use findlib,
which I only installed once.

Jacques