Re: [Caml-list] ocamlbuild generates .annot files in _build

[Romain Bardou <bardou@lsv.ens-cachan.fr>]

On 17/07/2012 09:00, Xavier Clerc wrote:
>
>
> ----- Mail original -----
>> On 07/17/2012 02:12 PM, Francois Berenger wrote:
>>> Hello,
>>>
>>> Shouldn't it generate theses files where the source files
>>> are?
>>>
>>> The emacs plugin can no more find the types in case
>>> the .annot files are not where the source file is.
>>
>> Also, the preprocessor INCLUDE directives don't work anymore because
>> ocamlbuild did not copy the .ml file to include in _build.
>>
>> You have to use INCLUDE "../[your_file]" instead, which is dirty.
>
> I don't know if you will find my suggestion clean,
> but when I encounter a similar problem I design an
> ocamlbuild plugin that just copies the file to the
> build directory.
>
> This will avoid relying upon a relative path, and
> fits ocamlbuild structure by just declaring a dependency
> and a rule to barely copy the file from its original
> place to the build directory. Notice that this is akin
> to what ocamlbuild actually does for source file, the
> only difference is that ocamlbuild cannot determine the
> dependency in your case. Hence, you have to declare it
> manually.

It feels very odd, at first, that the "dep" function of the Ocamlbuild 
API declares a dependency for tags rather than for a given file. I 
understand the rationale, it is strictly more general as this allows to 
add a dependency to a file only in some specific context, i.e. for 
specific rules. But we have to tag the file first (unless all files are 
tagged with their own name? I don't remember). Tagging a file to be able 
to declare a dependency does not feel very intuitive to me.

I'm not even sure this works with every rules, I'm a little blurry on 
how tags are added to commands. Are all tags of the file names which 
appear in the command added automatically?

Cheers,

-- 
Romain Bardou