From aa536b1d46cd50d5f34947eb5b2c6ef886d81d97 Mon Sep 17 00:00:00 2001 From: Carl Gay Date: Mon, 29 Apr 2024 11:27:27 -0400 Subject: [PATCH] doc: more dylan-tool -> deft changes --- README.md | 4 ++-- .../source/managing-dependencies.rst | 19 +++++++++--------- .../source/platform-specific.rst | 6 +++--- .../source/source-registries.rst | 20 +++++++++---------- 4 files changed, 24 insertions(+), 25 deletions(-) diff --git a/README.md b/README.md index fd1140f71..8491b3884 100644 --- a/README.md +++ b/README.md @@ -16,9 +16,9 @@ Verify that the downloaded version is working correctly by building a hello-world binary: ``` - dylan new application --simple hello-world + deft new application --simple hello-world cd hello-world - dylan build --all + deft build --all _build/bin/hello-world ``` diff --git a/documentation/getting-started-cli/source/managing-dependencies.rst b/documentation/getting-started-cli/source/managing-dependencies.rst index c6997af5c..78be33b26 100644 --- a/documentation/getting-started-cli/source/managing-dependencies.rst +++ b/documentation/getting-started-cli/source/managing-dependencies.rst @@ -2,13 +2,12 @@ Managing Dependencies ===================== We recommend managing inter-library dependencies by use of the Dylan package -manager and the :program:`dylan` tool. When using the :program:`dylan` tool -dependencies are added to the "dylan-package.json" file in your project. Each -dependency includes a `semantic version `_ and `dependency -resolution -`_ -is done with "minimal version selection". See the `dylan-tool`_ documentation -for details. +manager and :program:`deft`. When using :program:`deft` dependencies are added +to the "dylan-package.json" file in your project. Each dependency includes a +`semantic version `_ and `dependency resolution +`_ is +done with "minimal version selection". See the `deft`_ documentation for +details. The second way to manage dependencies is to use Git submodules. The remainder of this document explains how to do that. @@ -70,8 +69,8 @@ Transitive Dependencies ----------------------- The Dylan compiler won't find transitive dependencies automatically (unless you -are using `dylan-tool`_), so you will need to create registry entries for them -as well. +are using `deft`_), so you will need to create registry entries for them as +well. Sometimes, you will want to create git submodules for them as well, but other times you can just reference them from the @@ -82,4 +81,4 @@ a number of submodules, so you don't need to pull each of those in directly, but can reference them through the ``ext/http/`` directory. -.. _dylan-tool: https://opendylan.org/package/dylan-tool/index.html +.. _deft: https://opendylan.org/package/deft/index.html diff --git a/documentation/getting-started-cli/source/platform-specific.rst b/documentation/getting-started-cli/source/platform-specific.rst index 7e4442113..b6aeccc9c 100644 --- a/documentation/getting-started-cli/source/platform-specific.rst +++ b/documentation/getting-started-cli/source/platform-specific.rst @@ -66,9 +66,9 @@ For further details of the LID file format, see :doc:`../library-reference/lid`. 4) The ``Platforms`` keyword Platform-specific LID files should use the ``Platforms`` keyword to indicate - which platforms they apply to. This tells the `dylan update - `_ - command which registry files to create. + which platforms they apply to. This tells the `deft update + `_ command which + registry files to create. =============== ========================= ========================= Keyword unix-io.lid win32-io.lid diff --git a/documentation/getting-started-cli/source/source-registries.rst b/documentation/getting-started-cli/source/source-registries.rst index 00340f999..6bd4ae008 100644 --- a/documentation/getting-started-cli/source/source-registries.rst +++ b/documentation/getting-started-cli/source/source-registries.rst @@ -1,11 +1,11 @@ Using Source Registries ======================= -.. note:: When using the :program:`dylan` tool source registries are created - for you via the `dylan update - `_ - command and you should not have to create them explicitly. You may - want to skip this section for now. +.. note:: When using :program:`deft`, source registries are created for you via + the `deft update + `_ command + and you should not have to create them explicitly. You may want to + skip this section for now. Passing the name of a ".lid" file to :program:`dylan-compiler` works great when you have a single library that only uses other libraries that are part of Open @@ -17,8 +17,8 @@ For each Dylan library that isn't part of Open Dylan itself, you create a file in the registry which is named the same as the library and contains a pointer to the ".lid" file for the library. For example, here's the registry file for hello-world, created in the previous section. Note that this assumes you are -still in the directory created by `dylan new application -`_. +still in the directory created by `deft new application +`_. :: @@ -26,9 +26,9 @@ still in the directory created by `dylan new application registry/x86_64-darwin/hello-world What's going on here? First of all, the registry mechanism makes it possible -to have platform-specific libraries. The `dylan -`_ tool currently always -writes registry entries to a platform-specific directory, in this case +to have platform-specific libraries. `deft +`_ currently always writes +registry entries to a platform-specific directory, in this case ``x86_64-darwin``, but anything platform-independent can actually go in the :file:`registry/generic` subdirectory.