-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve support for "Platforms:" in LID file #3
Comments
We could also use a way to indicate that a LID doesn't support a specific platform. For example we have a lot of libraries that only support x86-win32 and rather than listing all the other platforms in the non-x86-win32 LID file we could use one of these:
The specific syntax probably doesn't matter too much. |
These LID files are included in other platform-specific LID files (usually win32 LID files) and hence dylan-tool decides they aren't applicable to Unix platforms unless those platforms are specifically listed. See https://github.com/dylan-lang/dylan-tool/issues/78
These LID files are included in other platform-specific LID files (usually win32 LID files) and hence dylan-tool decides they aren't applicable to Unix platforms unless those platforms are specifically listed. See https://github.com/dylan-lang/dylan-tool/issues/78
These LID files are included in other platform-specific LID files (usually win32 LID files) and hence dylan-tool decides they aren't applicable to Unix platforms unless those platforms are specifically listed. See https://github.com/dylan-lang/dylan-tool/issues/78
I would like to add support for these special platforms keywords:
When this is done, or even partly done, update the documentation here: https://opendylan.org/library-reference/lid.html#standard-lid-keywords |
Also, would it make sense to write a registry file for each covered platform if the spec is not Currently deft only writes a registry file for the current platform, in the platform-specific registry directory. |
This would avoid having to list all the platforms and would allow us to write the registry entry in the
registry/generic/
. It's also nice for self-documenting purposes compared to "here's a list of platforms; you decide if it's complete".The text was updated successfully, but these errors were encountered: