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

provide use_ocamlfind as a tag #6890

Closed
vicuna opened this issue Jun 4, 2015 · 2 comments
Closed

provide use_ocamlfind as a tag #6890

vicuna opened this issue Jun 4, 2015 · 2 comments

Comments

@vicuna
Copy link

vicuna commented Jun 4, 2015

Original bug ID: 6890
Reporter: @bobzhang
Status: resolved (set by @damiendoligez on 2017-03-01T12:36:07Z)
Resolution: suspended
Priority: normal
Severity: feature
Category: -for ocamlbuild use https://github.com/ocaml/ocamlbuild/issues

Bug description

it would be nice that I can write
true: use_ocamlfind
so I don't need type ocamlbuild -use-ocamlfind everytime, thanks -- Hongbo

@vicuna
Copy link
Author

vicuna commented Jun 4, 2015

Comment author: @gasche

I declined to implement this feature request in the past, because it steps away from the current intended semantics of _tags file, which is to add tags to targets that are then turned into compilation flags by the flag rules declared by the user. use_ocamlfind would not affect the compilation of any particular target, it would globally change the set of rules.

I'm getting tired of this and I don't have the time to work on a system that would both preserve (or coherently expand) the semantics and answer the user's needs -- and also arguably there is the use_menhir precedent -- so I'm thinking of just doing that. In any case, patches would be welcome (should not be too hard).

@vicuna
Copy link
Author

vicuna commented Mar 1, 2017

Comment author: @damiendoligez

ocamlbuild is now a separate project that lives in GitHub.
PR transferred to ocaml/ocamlbuild#185

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

1 participant