The Atlas Package cloner. It manages project dependencies in an isolated deps/ directory.
Upcoming Nim version 2.0 will ship with atlas. Building from source:
git clone https://github.com/nim-lang/atlas.git
cd atlas
nim c src/atlas.nim
# copy src/atlas[.exe] somewhere in your PATHRead the full documentation or go through the following tutorial.
Create a new project. A project contains everything we need and can safely be deleted after this tutorial:
mkdir project
cd project
atlas initCreate a new project inside the project:
mkdir myproject
cd myprojectTell Atlas we want to use the "malebolgia" library:
atlas use malebolgiaNow import malebolgia in your Nim code and run the compiler as usual:
echo "import malebolgia" >myproject.nim
nim c myproject.nimThe project structure looks like this:
$project / project.nimble
$project / nim.cfg
$project / other main project files...
$project / deps / atlas.config
$project / deps / dependency-A
$project / deps / dependency-B
$project / deps / dependency-C.nimble-link (for linked projects)
atlas use https://github.com/zedeus/nitter
atlas link ../../existingDepdency/Sometimes it's helpful to understand what Atlas is doing. You can run commands with: atlas --verbosity:<trace|debug> to get more information.
atlas env 2.0.0
source deps/nim-2.0.0/activate.shAtlas places dependencies in a deps/ directory. This is especially helpful for working with projects that have dependencies pinned as git submodules, which was common in the pre-Atlas era.
The deps/ directory contains:
atlas.config: Configuration file for dependency management- Individual dependency directories
nimble-linkfiles for linked projects
Note that atlas.config file can be placed in the main project directory as well. In this case, the dependencies directory can modified by setting the deps field.