Skip to content
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

Open
vicuna opened this issue Sep 25, 2013 · 7 comments
Open

Comments

@vicuna
Copy link

vicuna commented Sep 25, 2013

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.

@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label May 15, 2020
@shindere
Copy link
Contributor

shindere commented Jun 4, 2020 via email

@github-actions github-actions bot removed the Stale label Jun 17, 2020
@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Jul 21, 2021
@shindere
Copy link
Contributor

shindere commented Aug 9, 2021 via email

@github-actions github-actions bot removed the Stale label Aug 11, 2021
@github-actions
Copy link

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.

@github-actions github-actions bot added the Stale label Aug 19, 2022
@shindere
Copy link
Contributor

shindere commented Aug 29, 2022 via email

@shindere shindere removed the Stale label Aug 29, 2022
@dbuenzli
Copy link
Contributor

@dbuenzli?

I don't think I have used make for building OCaml since 2007 so someone else may know better. Generally I just use the -modules output and massage it to my needs.

I guess if you want to add something for the make output it could be -build-path-prefix DIR (inspired by the name of the BUILD_PATH_PREFIX_MAP env var).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants