Skip to content

GitLab

Switch branch/tag
  1. 14 Feb, 2017 1 commit
  3. 12 Feb, 2017 1 commit
    • 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
  5. 09 Feb, 2017 1 commit
  7. 06 Feb, 2017 1 commit
  9. 21 Jan, 2017 1 commit
  11. 11 Jan, 2017 2 commits
  13. 10 Jan, 2017 1 commit
  15. 15 Dec, 2016 1 commit
  17. 14 Dec, 2016 1 commit
  19. 10 Dec, 2016 1 commit
  21. 29 Nov, 2016 4 commits
  23. 16 Nov, 2016 1 commit
  25. 04 Nov, 2016 1 commit
  27. 02 Nov, 2016 1 commit
  29. 28 Oct, 2016 2 commits
  31. 27 Oct, 2016 1 commit
  33. 25 Oct, 2016 2 commits
  35. 17 Oct, 2016 1 commit
  37. 14 Oct, 2016 1 commit
  39. 12 Oct, 2016 2 commits
  41. 11 Oct, 2016 1 commit
  43. 10 Oct, 2016 1 commit
    • Jeromy's avatar
      bitswap: protocol extension to handle cids · a3c90040
      Jeromy authored 
      This change adds the /ipfs/bitswap/1.1.0 protocol. The new protocol
adds a 'payload' field to the protobuf message and deprecates the
existing 'blocks' field. The 'payload' field is an array of pairs of cid
prefixes and block data. The cid prefixes are used to ensure the correct
codecs and hash functions are used to handle the block on the receiving
end.

License: MIT
Signed-off-by: default avatarJeromy <why@ipfs.io>
      a3c90040
  45. 08 Oct, 2016 1 commit
  47. 06 Oct, 2016 4 commits
  49. 09 Sep, 2016 1 commit
  51. 07 Sep, 2016 2 commits
  53. 26 Aug, 2016 1 commit
  55. 23 Aug, 2016 1 commit
  57. 20 Aug, 2016 1 commit