Skip to content
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

Add convenient makefile arguments for packaging #414

Merged
merged 2 commits into from
Jun 25, 2020

Conversation

bcardiff
Copy link
Member

Similar to crystal-lang/crystal#9471
Follow-up to crystal-lang/distribution-scripts#71 (comment)

I'm only adding release, debug, static to use the same in crystal repo. But I think having FLAGS is enough.

When packaging shards is usually compiled with --no-debug and --release. This change will allow using the makefile in those scripts.

Otherwise we need to manually use the crystal build or CRYSTAL_OPTS env var
Same as the ones found in crystal-lang/crystal
@bcardiff bcardiff merged commit ee6d18f into crystal-lang:master Jun 25, 2020
@waj waj added this to the v0.12.0 milestone Jul 28, 2020
@bcardiff bcardiff deleted the feature/makefile-flags branch August 5, 2020 14:20
taylor pushed a commit to vulk/shards that referenced this pull request Aug 11, 2020
* Allow make all FLAGS="--no-debug --release" 

When packaging shards is usually compiled with --no-debug and --release. This change will allow using the makefile in those scripts.

Otherwise we need to manually use the crystal build or CRYSTAL_OPTS env var

* Add release debug static makefile arguments

Same as the ones found in crystal-lang/crystal
f-fr pushed a commit to f-fr/shards that referenced this pull request Jan 2, 2021
* Allow make all FLAGS="--no-debug --release" 

When packaging shards is usually compiled with --no-debug and --release. This change will allow using the makefile in those scripts.

Otherwise we need to manually use the crystal build or CRYSTAL_OPTS env var

* Add release debug static makefile arguments

Same as the ones found in crystal-lang/crystal
@taylorthurlow
Copy link

Looks like the README build instructions are now wrong due to these changes.

@bcardiff
Copy link
Member Author

Good catch @taylorthurlow. The README is indeed outdated regarding the CRFLAGS (since #344).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants