New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing argument for ocamldep to tell it where output binaries will be placed #6191
Comments
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Yes, this is of course still an issue and I definitely want to work on
it.
The `-odir` option should probably be common also to the compilers. Such
an option would simplify the life of all the OCaml-related build
systems, it's toob ad it hasn't been implemented way earlier, rather
than all the hackery that was created to leave without it with copying
and symlinking files.
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Yes, this still needs to be addressed, I think.
|
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Hopefully for the last time yes, we (Ii) need to address this.
This belongs to the bigger story of being able to separate source and
build trees.
The need for this distinction is relevant not only for OCaml projects,
but for the OCaml compiler itself.
For the compiler we have at the moemnt decided *not* to implement a
`-odir` option. The only thing we have at the moment is the `-o` option
to say where an output file should be written, and the `-cmi-file`
option to tell which `.cmi` file should be used when checking that a
`.ml` file matches its signature.
So, the right interface to use for `ocamldep` still needs to be figured
out.
Any thoughts welcome.
@dbuenzli?
|
I don't think I have used I guess if you want to add something for the |
Original bug ID: 6191
Reporter: kosik
Assigned to: @shindere
Status: assigned (set by @damiendoligez on 2017-03-24T12:06:48Z)
Resolution: open
Priority: low
Severity: feature
Version: 3.12.1
Category: tools (ocaml{lex,yacc,dep,debug,...})
Related to: #3757 #3904 #5890
Bug description
ocamldep currently assumes that both, the source code files (*.ml, .mli) and the generated binaries (.cmi, *.cmo, *.cmx) will reside in the same directory.
Sometimes people place output binaries to a separate directory
(that makes sense to me when we want to switch back and forth
among git branches while we do not want to see unrelated binaries
in the source code tree)
and then the ocamldep's output does not make sense.
The generated ocamldep output can be easily corrected with "sed" but, ideally, that extra step should not be necessary.
If there existed some (? -odir ?) parameter that ocamldep would understand and took into account, that would probably be perfect.
The text was updated successfully, but these errors were encountered: