[MIRROR] nimbus – a Nim build system https://nimbus.sysrq.in/
Go to file
Anna “CyberTailor” 1e65c6c43a
Bump version: 1.1.1 → 1.1.2
2023-05-28 16:49:38 +05:00
.reuse nimbus.nim: use custom jsonscript executor 2023-04-27 23:00:30 +05:00
LICENSES Implement Ninja code generator 2022-06-29 03:34:39 +05:00
docs ci: add a step for Sphinx docs 2023-05-08 09:22:34 +05:00
man nimbus.nim: separate Nim cache by binary 2023-04-27 22:48:19 +05:00
src nimbus.nim: re-add variable 2023-05-28 16:42:46 +05:00
tests nimbus.nim: separate Nim cache by binary 2023-04-27 22:48:19 +05:00
.bumpversion.cfg Bump version: 1.1.1 → 1.1.2 2023-05-28 16:49:38 +05:00
.drone.yml ci: add a step for Sphinx docs 2023-05-08 09:22:34 +05:00
.gitignore docs/*: add Sphinx docs 2022-11-13 19:38:17 +05:00
ChangeLog nimbus.nim: re-add variable 2023-05-28 16:42:46 +05:00
README.md Add build status to README.md 2023-05-02 19:24:02 +05:00
nimbus.nimble Bump version: 1.1.1 → 1.1.2 2023-05-28 16:49:38 +05:00

README.md

nimbus

Build Status

nimbus is a Nim build system. You can also call in NimBS. Nimja would also be a clever name but it's already taken (turns out the name "nimbus" is taken two times already but nobody cares yet).

Raison d'être

nimble is a great tool for development but it does not get on well with system package managers.

This project is intended to be used with traditional package managers (primarly with Gentoo's Portage). But maybe it'll be useful for other purposes too.

Dependencies

nimbus only generates build.ninja files, so you'll need ninja or samurai to use it.

Installing

  • Using nimble:

    nimble install

  • Using just Nim compiler:

    nim c src/nimbus
    nim c src/txt2deps
    

Testing

$ testament all

Packaging

You can track new releases using an atom feed provided by GitHub.

Contributing

Patches and pull requests are welcome. Please use either git-send-email(1) or git-request-pull(1), addressed to cyber@sysrq.in.

Your commit message should conform to the following standard:

file/changed: Concice and complete statement of the purpose

This is the body of the commit message.  The line above is the
summary.  The summary should be no more than 72 chars long.  The
body can be more freely formatted, but make it look nice.  Make
sure to reference any bug reports and other contributors.  Make
sure the correct authorship appears.

IRC

You can join the #nimbus channel either on OFTC or via Matrix.

License

  • BSD-3-Clause
  • Apache-2.0 (ninja_syntax.nim)