From 10bc790d3fe05efb23751c6937093be19aa530a9 Mon Sep 17 00:00:00 2001
From: cgay
Date: Wed, 19 Jun 2024 17:14:26 +0000
Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20dylan-la?=
=?UTF-8?q?ng/opendylan@3398f641c3f5a3bb55d9fdacf4d78c5a78ee2850=20?=
=?UTF-8?q?=F0=9F=9A=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
.../platform-specific.rst.txt | 8 +++--
_sources/library-reference/lid.rst.txt | 32 +++++++++++++++++
getting-started-cli/platform-specific.html | 6 ++--
library-reference/lid.html | 36 +++++++++++++++++++
searchindex.js | 2 +-
5 files changed, 78 insertions(+), 6 deletions(-)
diff --git a/_sources/getting-started-cli/platform-specific.rst.txt b/_sources/getting-started-cli/platform-specific.rst.txt
index 9cd8bf132..e2b4fd00b 100644
--- a/_sources/getting-started-cli/platform-specific.rst.txt
+++ b/_sources/getting-started-cli/platform-specific.rst.txt
@@ -66,9 +66,11 @@ 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 `deft update
- `_ command which
- registry files to create.
+ which platforms they apply to. This helps the `deft update
+ `_ command decide
+ which registry files to create. If there is no ``Platforms`` keyword
+ ``deft`` assumes the LID file applies to the current platform and creates a
+ registry file for its library.
=============== ========================= =========================
Keyword unix-io.lid win32-io.lid
diff --git a/_sources/library-reference/lid.rst.txt b/_sources/library-reference/lid.rst.txt
index a44b01bbe..3b84a11f8 100644
--- a/_sources/library-reference/lid.rst.txt
+++ b/_sources/library-reference/lid.rst.txt
@@ -168,6 +168,38 @@ Open Dylan's LID extensions
This section contains extensions to LID that Open Dylan supports.
+Tooling Support
+---------------
+
+Platforms
+^^^^^^^^^
+
+Platform-specific LID files should use the ``Platforms`` keyword to indicate
+which platforms they apply to. This helps the `deft update
+`_ command decide
+which registry files to create. If there is no ``Platforms`` keyword ``deft``
+assumes the LID file applies to the current platform and creates a registry
+file for its library.
+
+For example, if you have a library with separate LID files for Windows and Unix
+platforms add this to the Windows LID file::
+
+ Platforms: win32
+
+and add this to the Unix LID file::
+
+ Platforms: x86_64-linux
+ x86_64-darwin
+ x86_64-freebsd
+ x86_64-netbsd
+ x86-freebsd
+ x86-linux
+ x86-netbsd
+
+.. note:: We `plan `_ to add
+ platform aliases such as "unix" so that it isn't necessary to list
+ all supported Unix platforms.
+
Specifying foreign files and resource files
-------------------------------------------
diff --git a/getting-started-cli/platform-specific.html b/getting-started-cli/platform-specific.html
index 730f2f0ea..b70bfa81c 100644
--- a/getting-started-cli/platform-specific.html
+++ b/getting-started-cli/platform-specific.html
@@ -657,8 +657,10 @@ LID File
Platform-specific LID files should use the Platforms
keyword to indicate
-which platforms they apply to. This tells the deft update command which
-registry files to create.
+which platforms they apply to. This helps the deft update command decide
+which registry files to create. If there is no Platforms
keyword
+deft
assumes the LID file applies to the current platform and creates a
+registry file for its library.
diff --git a/library-reference/lid.html b/library-reference/lid.html
index 6553da0aa..0ea18db56 100644
--- a/library-reference/lid.html
+++ b/library-reference/lid.html
@@ -676,6 +676,38 @@ Comment: