server: resolve Lazarus package links from config#156
Open
corpix wants to merge 2 commits into
Open
Conversation
Load Lazarus package links from packagefiles.xml and global link files when configuring project search paths. Prefering explicit config package links over discovered and global links. Resolve package paths relative to their config or package location, and expand Lazarus/FPC/target/project macros while preserving unknown macros as-is. Add LazConfig tests for package-link priority, config-file based packagefiles.xml discovery, and macro expansion. Register missing RemoveUnusedUnits files in the server package.
corpix
force-pushed
the
feature/lazarus-package-links
branch
from
5cfe323 to
131539d
Compare
Owner
|
See what @mvancanneyt has to say as I don't use Lazarus myself. |
- add system/user/project .pasls.cfg loading with project overrides - save selected main program into repo .pasls.cfg - infer compiler, target, FPC source dir, and main program where possible - improve cross-platform FPC source path inference, including Lazarus-adjacent layouts - configure workspace .lpk paths when no single main program is selected - resolve package dependencies before applying workspace package paths - add regression coverage for project config persistence and workspace package dependency paths
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi. I've been struggling with navigation inside doublecmd sources, so I made some changes to support lazarus projects, here are quick summary:
Load Lazarus package links from packagefiles.xml and global link files when configuring project search paths. Prefering explicit config package links over discovered and global links.
Resolve package paths relative to their config or package location, and expand Lazarus/FPC/target/project macros while preserving unknown macros as-is.
Add LazConfig tests for package-link priority, config-file based packagefiles.xml discovery, and macro expansion. Register missing RemoveUnusedUnits files in the server package.
What do you think?