Re: Arguments to configure

[Vivien Kraus]

Sébastien Hinderer writes:
>
> 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?

I like OCaml very much, so I could not help but reply again to the
thread :)  Sorry if it's uninformative / not the proper way to do it.

Can this target-bindir be configured when running the program?  Like:

ocamlc --target-bindir="/whatever/bin" myapp.ml

I could not find such an option in ocamlc options, but maybe it's under
a different name.  Or deep down in a to-do list.

Anyway, it looks like a default hard-coded value for a run-time option
of the program that the user / distribution might wish to change.  I would
put it in a --enable-default-target-bindir="/whatever/bin" option or
DEFAULT_TARGET_BINDIR="/whatever/bin" variable, and then in the program
code use a command-line option to override it.  (see autogen / autoopts
which is great if you want more:
https://www.gnu.org/software/autogen/manual/html_node/AutoOpts.html#AutoOpts).

I think it is different from the other target-specific options like what
kind of code the program should produce, which is not something that the
user would like to change when running the program.

Anyway, this is what I would do, with my limited knowledge about
cross-compilers :)

Vivien