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

Jump to bottom

Make the dependency generator for OCaml better usable for out-of-source builds #7577

Closed
vicuna opened this issue Jul 2, 2017 · 5 comments
Closed

Make the dependency generator for OCaml better usable for out-of-source builds #7577

vicuna opened this issue Jul 2, 2017 · 5 comments
Labels
feature-wish tools

Comments

@vicuna
Copy link

vicuna commented Jul 2, 2017 •
edited by nojb

Original bug ID: 7577
Reporter: @elfring
Status: closed (set by @dra27 on 2017-07-03T10:38:54Z)
Resolution: not a bug
Priority: normal
Severity: feature
Version: 4.03.0
Category: tools (ocaml{lex,yacc,dep,debug,...})

Bug description

I started to experiment a bit more for build script adjustments for another free software.

elfring@Sonne:~/Projekte/Bau/OCamlbuild> ocamldep -one-line -I ~/Projekte/OCaml/OCamlbuild/lokal/src ~/Projekte/OCaml/OCamlbuild/lokal/src/command.mli
/home/elfring/Projekte/OCaml/OCamlbuild/lokal/src/command.cmi : /home/elfring/Projekte/OCaml/OCamlbuild/lokal/src/tags.cmi /home/elfring/Projekte/OCaml/OCamlbuild/lokal/src/signatures.cmi

This tool is writing references for compiled interface descriptions with paths of the source file directory.
How can be achieved that this program will use the working directory (or an other specification for the desired software build folder) for these cmi files?
@vicuna
Copy link
Author

vicuna commented Jul 3, 2017

Comment author: @dra27

You have repeatedly been asked to post questions to caml-list (which I know you're on) or discuss.ocaml.org

@vicuna
Copy link
Author

vicuna commented Jul 3, 2017 •
edited by nojb

Comment author: @elfring

I have reported a specific detail in the data display which I find inappropriate in the mentioned use case.
Please let us fix the affected software somehow.

@vicuna
Copy link
Author

vicuna commented Jul 3, 2017

Comment author: @dra27

You have not reported anything - you have asked a question as to whether ocamldep can work as you require and I have told you to ask your question elsewhere.

Please stop re-opening these reports.

@vicuna vicuna closed this as completed Jul 3, 2017
@elfring
Copy link

elfring commented Apr 15, 2019

Can the clarification of affected software components be continued also for this issue?

@dra27
Copy link
Member

dra27 commented Apr 15, 2019

This issue doesn’t need continuing - it was closed with a specific remedy which as far as I’m aware hasn’t been followed.

@ocaml ocaml locked as off-topic and limited conversation to collaborators Apr 15, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
feature-wish tools
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elfring @dra27 @vicuna