summary refs log tree commit diff stats
path: root/nim.nimble
Commit message (Collapse)AuthorAgeFilesLines
* Create compiler and nimsuggest packages (#22118)Ivan Yonchovski2023-06-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I have tested it locally with the following in my local packages_official.json ``` { "name": "compiler", "url": "https://github.com/yyoncho/Nim.git/?subdir=compiler", "method": "git", "tags": [ "library", "compiler" ], "description": "Package providing the Nim compiler binaries plus all its source files that can be used as a library", "license": "MIT", "web": "https://github.com/nim-lang/Nim" }, { "name": "nimsuggest", "url": "https://github.com/yyoncho/Nim.git/?nimsuggest=compiler", "method": "git", "tags": [ "library", "compiler" ], "description": "Package providing the Nim compiler binaries plus all its source files that can be used as a library", "license": "MIT", "web": "https://github.com/nim-lang/Nim" }, ``` Then `nimble install compiler`, `nimble install nimsuggest` work as expected.
* Avoid calling build_all* when nim binary is present (#21522)Ivan Yonchovski2023-03-201-2/+4
| | | | - `nimble` will build `nim` using `bin/nim` and if it is already present we can reuse it.
* Define the version of nim package without using system module (#21415)Ivan Yonchovski2023-03-021-1/+2
| | | This is follow up from https://github.com/nim-lang/Nim/pull/21313
* Fix the nimble build on Windows (#21314)Ivan Yonchovski2023-02-011-1/+1
| | | | | Fix the build on Windows - `nimble install` fails on Windows, the `./` is not needed.
* the devel branch now uses csources_v2 (#21108)ringabout2022-12-161-1/+1
| | | | | | | * the devel branch now uses csources_v2 * fixes hash * bump csources_v2
* Change nim's nimble files to make it installable (#20179)Ivan Yonchovski2022-08-311-0/+14
- needs #20168 to make the stuff working I went for this minimal solution because it seems like `compiler.nimble` and `nimsuggest.nimble` are not in use Co-authored-by: Clay Sweetser <Varriount@users.noreply.github.com>