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

Move sample generation of README in its own package #3

Merged
merged 3 commits into from
Nov 13, 2019

Conversation

regisd
Copy link
Contributor

@regisd regisd commented Oct 15, 2018

Discussed in #1, the problem with building //... is that bazel downloads all the build toolchains, even though only one is useful for the host.

By moving the sample generation in //sample, anyone can run bazel build //sample/... and only download what is needed to produce the README file in all formats.

Also, exports PANDOC_FORMATS so that the rule and the sample use the same set of formats.

The problem with building `//...` is that bazel downloads all the build toolchains, even though only one is useful for the host.

By moving the sample generation in //sample, anyone can run `bazel build //sample/...` and only download what is needed to produce the README file in all formats.

Also, exports PANDOC_FORMATS so that the rule and the sample use the same set of formats.
@regisd
Copy link
Contributor Author

regisd commented Oct 15, 2018

This change depends on #4

@patbro patbro merged commit cb39f15 into ProdriveTechnologies:master Nov 13, 2019
@regisd regisd deleted the mv-sample branch November 18, 2019 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants