Skip to content

GitLab

Switch branch/tag
  1. 12 Aug, 2017 1 commit
  3. 09 Aug, 2017 2 commits
  5. 17 Jul, 2017 1 commit
    • Steven Allen's avatar
      gx: update ipldcbor · 840b169d
      Steven Allen authored 
      I previously optimized the IPLD cbor decoder to *not* encode and then re-decode
objects when constructing them with `WrapObject`. Unfortunately, we rely on this
to canonicalize the object before computing the tree/links.

License: MIT
Signed-off-by: default avatarSteven Allen <steven@stebalien.com>
      840b169d
  7. 12 Jul, 2017 2 commits
  9. 05 Jul, 2017 3 commits
  11. 04 Jul, 2017 1 commit
  13. 03 Jul, 2017 1 commit
  15. 01 Jul, 2017 1 commit
  17. 29 Jun, 2017 2 commits
  19. 31 May, 2017 1 commit
  21. 18 May, 2017 3 commits
  23. 14 May, 2017 1 commit
  25. 26 Apr, 2017 4 commits
  27. 20 Apr, 2017 1 commit
  29. 07 Mar, 2017 1 commit
  31. 02 Mar, 2017 3 commits
  33. 17 Feb, 2017 2 commits
  35. 16 Feb, 2017 1 commit
  37. 14 Feb, 2017 4 commits
  39. 12 Feb, 2017 2 commits
    • Jeromy's avatar
      update go-multihash and bubble up deps · fcea3278
      Jeromy authored 
      License: MIT
Signed-off-by: default avatarJeromy <jeromyj@gmail.com>
      fcea3278
    • Jakub Sztandera's avatar
      make: rework makefiles for non-recursive make and add sharness coverage · 99cea5f1
      Jakub Sztandera authored 
      This commit introduces non-recursive Makefile infrastructure that replaces current Makefile infrastructure.
It also generally cleanups the Makefiles, separates them into nicer sub-modules and centralizes common operations into single definitions.

It allows to depend on any target that is defined in the makefile, this means that for example `gx install` is called once when `make build test_expensive_sharness` is called instead of 4 or 5 times.

It also makes the dependencies much cleaner and allows for reuse of modules. For example sharness coverage collection (WIP) uses sharness target with amended PATH, previously it might have been possible but not without wiring in the coverage collection into sharness make runner code.

Yes, it is more complex but not much more. There are few rules that have to be followed and few complexities added but IMHO it is worth it.

How to NR-make:
1. If make is to generate some file via a target, it MUST be defined in Rules.mk file in the directory of the target.
2. `Rules.mk` file MUST have `include mk/header.mk` statement as the first line and `include mk/footer.mk` statement as the last line (apart from project root `Rules.mk`).
3. It then MUST be included by the closest `Rules.mk` file up the directory tree.
4. Inside a `Rules.mk` special variable accessed as `$(d)` is defined. Its value is current directory, use it so if the `Rules.mk` file is moved in the tree it still works without a problem. Caution: this variable is not available in the recipe part and MUST NOT be used. Use name of the target or prerequisite to extract it if you need it.
5. Make has only one global scope, this means that name conflicts are a thing. Names SHOULD  follow `VAR_NAME_$(d)` convention. There are exceptions from this rule in form of well defined global variables. Examples: General lists `TGT_BIN`, `CLEAN`; General targets: `TEST`, `COVERAGE`; General variables: `GOFLAGS`, `DEPS_GO`.
3. Any rules, definitions or variables that fit some family SHOULD be defined in `mk/$family.mk` file and included from project root `Rules.mk`

License: MIT
Signed-off-by: default avatarJakub Sztandera <kubuxu@protonmail.ch>
      99cea5f1
  41. 09 Feb, 2017 1 commit
  43. 06 Feb, 2017 1 commit
  45. 21 Jan, 2017 1 commit