hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 01:12:56 +03:00
Code Issues Projects Releases Wiki Activity
07328fd9fc
graphql-engine/scripts/make/build.mk

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

62 lines
2.2 KiB
Makefile
Raw Normal View History

server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
# Enable secondary expansion.
.SECONDEXPANSION:
PACKAGE_YAML_FILES = $(wildcard server/lib/*/package.yaml)
GENERATED_CABAL_FILES = $(foreach package_file,$(PACKAGE_YAML_FILES),$(wildcard $(dir $(package_file))*.cabal))
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
.PHONY: build-all
## build-all: build all haskell packages, or "have i broken anything?"
build-all: build build-tests build-integration-tests build-pro build-pro-tests build-multitenant build-multitenant-integration-tests
.PHONY: build
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
## build: build non-pro graphql executable
build: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build graphql-engine
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
.PHONY: build-tests
## build-tests: build non-pro graphql executable tests
build-tests: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build graphql-engine-tests
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
.PHONY: build-integration-tests
## build-integration-tests: build hspec integration tests
build-integration-tests: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build tests-hspec
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
.PHONY: build-pro
## build-pro: build pro graphql executable
build-pro: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build graphql-engine-pro
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
.PHONY: build-pro-tests
## build-pro-tests: build pro graphql executable tests
build-pro-tests: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build graphql-engine-pro-test
.PHONY: build-multitenant
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
## build-multitenant: build multitenant graphql executable
build-multitenant: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build graphql-engine-multitenant
.PHONY: build-multitenant-integration-tests
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
## build-multitenant-integration-tests: build multitenant integration tests
build-multitenant-integration-tests: $(GENERATED_CABAL_FILES)
tooling: Add `make build...` commands PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4824 GitOrigin-RevId: eeee7c47fb8b8160d85aee2d9d07fdf9ed14a703
2022-07-04 14:44:15 +03:00
cabal build multitenant-integration-test
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
# This makes use of Make's static pattern rules. Effectively, it is generating
# multiple rules, of the form:
#
# path/to/foo/foo.cabal: path/to/foo/package.yaml
# hpack ...
# path/to/bar/bar.cabal: path/to/bar/package.yaml
# hpack ...
#
# In order to call `dir`, it uses secondary expansion.
#
# See the documentation for more information:
# https://www.gnu.org/software/make/manual/html_node/Static-Pattern.html
# https://www.gnu.org/software/make/manual/html_node/Secondary-Expansion.html
$(GENERATED_CABAL_FILES): %.cabal: $$(dir %)/package.yaml
./scripts/hpack.sh $@
@ touch $@ # Required because `hpack` will not change the modified timestamp if the file is up-to-date.
Reference in New Issue Copy Permalink