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

Parser accepts no explicit outputs. #1159

Merged
merged 1 commit into from
May 27, 2016

Conversation

nicolasdespres
Copy link
Contributor

There is a class of commands that take an output directory where
they create their output files. Among them are cp(1), tar(1) to name a
few. These commands have one or more implicit outputs but no explicit
output.

With this patch, Ninja's parser accepts build edge with an
empty list of explicit outputs.

Discussed here: https://groups.google.com/forum/#!topic/ninja-build/Nt8QlmA5cQA

There is a class of commands that take an output directory where
they create their output files. Among them are cp(1), tar(1) to name a
few. These commands have one or more implicit outputs but no explicit
output.

With this patch, Ninja's parser accepts build edge with an
empty list of explicit outputs.
@bradking
Copy link
Contributor

The implementation and tests LGTM.

@nico nico merged commit 680efe4 into ninja-build:master May 27, 2016
@nico
Copy link
Collaborator

nico commented May 27, 2016

Thanks! I agree this makes sense.

@nicolasdespres nicolasdespres deleted the no-explicit-outputs branch May 29, 2016 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants