-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Add compiler detection of adjacent stdlib in dev folder #17071
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
Open
straight-shoota
wants to merge
7
commits into
crystal-lang:master
Choose a base branch
from
straight-shoota:feat/development-compiler-crystal_path
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
26254d3
Detect development use from executable path
straight-shoota cc884b1
Call `.build/crystal` directly instead of wrapper
straight-shoota 57498a7
Do not set `CRYSTAL_EXEC_PATH` when using wrapper with local compiler
straight-shoota 7d67736
Use `.build/crystal` in Windows CI
straight-shoota d428959
Makefile: Use `.build/crystal` directly for `primitive_spec`
straight-shoota 68d92bd
Run `make -C samples` directly instead of `make samples`
straight-shoota 0292d0d
Re-add `CRYSTAL_SPEC_COMPILER_BIN` in `win.yml`
straight-shoota File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not convinced. This would be hardcoded into every compiler while this is a configuration issue, and it's already handled by
CRYSTAL_CONFIG_PATHandCRYSTAL_PATH.I think the makefiles should export
CRYSTAL_CONFIG_PATH=$PWD/src:lib(when unset), and call sites should just configureCRYSTAL_PATH. Some helpers calling tocrystalalready do it.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CRYSTAL_CONFIG_PATHis for configuring the stdlib source path for packaging. We could customize it for development builds toCRYSTAL_CONFIG_PATH=$$ORIGIN/../src, but then it wouldn't work when installed at/usr/share/crystal/src, for example. We'd need separate configuration for production builds.You can either have a compiler build that picks up the local path, or one that is ready to be installed in a system path (or wherever).
Maybe, that's fine. But right now you can build a compiler, test it (with this patch, using
.build/crystal), and then install it. The automatic discover just works.Without automatic discovery,
.build/crystalwould not have any usable default configuration forCRYSTAL_PATH. TheCRYSTAL_CONFIG_PATHvalue doesn't work because it's not in an install location yet.Requiring explicit configuration is much more inconvenient compared to
bin/crystal.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if anybody's using the
installtarget to be honest. Distributions merely setCRYSTAL_CONFIG_PATH(e.g. alpine, debian, homebrew, ...).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that matter? I don't think the usage makes much difference whether you run
make installorinstall .build/crystal $out/bin/crystal🤷There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if nobody is using the
installtarget and instead configureCRYSTAL_CONFIG_PATH, then there's little point for theMakefileto keep using$$ORIGIN/../share/crystal/srcby default.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think they are two independent dimensions: Using
make installand relying on the defaultCRYSTAL_CONFIG_PATHare not directly related.There are use cases involving either one or both of them.