[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Arguments to configure
From: |
Sébastien Hinderer |
Subject: |
Re: Arguments to configure |
Date: |
Fri, 5 Oct 2018 08:14:43 +0200 |
Dear Gavin,
Many thanks for your response!
Gavin Smith (2018/10/04 19:10 +0100):
> On Wed, Oct 03, 2018 at 12:10:49PM +0200, Sébastien Hinderer wrote:
> > Coming to the directory I was talking about, it is currently called
> > "target-bindir" and is used to define where the bytecode interpreter,
> > ocamlrun, will reside on the target system. This is something the
> > compiler running on the host needs to know because it adds a line like
> > #!/path/to/ocamlrun/on/target/system
> > at the beginning of the bytecode executables it produces, so that they
> > can then be run as regular executable programs on the target. Does all
> > this make sense? Perhaps autoconf has a different way of handling such
> > settings?
>
> Could this be a subdirectory of one of the standard installation
> directories?
>
> https://www.gnu.org/prep/standards/html_node/Directory-Variables.html
>
> For example, your "target-bindir" could be set from libexecdir, and
> be /usr/local/libexec/ocamalrun by default.
Well to be honest I have so far not been able to discuss with the
developers who are actually using this feature. However, at first sight
I'd say I don't think this is something we want to enforce.
Thanks agian for your suggestion!
Sébastien.