Add LibPath for shared library initialization
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- fortran
- Domain
- operating-systems
Research direction
Start by locating the Math namespace's shared-library initialization and identify where the optional LibPath variable can be handled. Compare the current lookup behavior with the requested hierarchy, including the Windows-only locations and workspace fallback. Done means LibPath is optional and the listed search order is implemented.
Written by the indexing model from the issue text.
Description
Currently you need to put the shared libraries in one of a few specific places, some of which require administrator access. We should add an optional LibPath variable to the Math namespace. If specified, this is where Math will look first for the shared libraries.
Ideally I'd like to see the following search hierarchy implemented:
- LibPath, if non-empty
- the directory with the dyalog executable
- the current directory
- the Windows\System directory (Windows only)
- the Windows\ directory (Windows only)
- a directory in the operating system's PATH
- the directory where Math.dyalog was loaded from (if available)
- the directory of the current workspace (if applicable)
- Dominant language
- Fortran
- Stars
- 16
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Dyalog/Math
Similar issues
-
area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
crmne/zapfast#446 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ChrisTitusTech/winutil#5145 ·
Maintainers usually reply within 6 days
-
ktuner keeps a stale ledger path and can never restore that entryPossibly taken @Frun1na claimed this today. Opencomponent:ktuner
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
agentic-os-org/ANOLISA#6483 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100