-
Notifications
You must be signed in to change notification settings - Fork 303
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 platform-specific release configuration #1900
Merged
Merged
Conversation
This file contains 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
fhanau
force-pushed
the
felix/bazel-release-cfg
branch
6 times, most recently
from
March 31, 2024 20:06
5a286fa
to
450b564
Compare
fhanau
changed the title
[WIP] Add and overhaul platform-specific release and debug configurations
Add platform-specific release configuration
Mar 31, 2024
- Match macOS wd_benchmark link options with wd_binary options - Correct spelling of WIN32_LEAN_AND_MEAN - /await and /GF are ignored by clang-cl, no need to pass them in the Windows build.
fhanau
force-pushed
the
felix/bazel-release-cfg
branch
from
March 31, 2024 20:52
450b564
to
4cf42ff
Compare
jasnell
approved these changes
Apr 4, 2024
fhanau
added a commit
that referenced
this pull request
Apr 7, 2024
The original PR failed to apply the `release` configuration to release_unix, leading to a binary size regression, especially on macOS. This was caused by bazel using fastbuild mode instead of opt mode, Rust code was not being optimized and on macOS -DDEBUG was defined through the bazel toolchain defaults. - Fix a typo and clarify Windows release config comment Original commit message: - Match macOS wd_benchmark link options with wd_binary options - Correct spelling of WIN32_LEAN_AND_MEAN - /await and /GF are ignored by clang-cl, no need to pass them in the Windows build.
fhanau
added a commit
that referenced
this pull request
Apr 7, 2024
The original PR failed to apply the `release` configuration to `release_unix`, leading to a binary size regression, especially on macOS. This was caused by bazel using fastbuild mode instead of opt mode, leading to Rust code not being optimized and -DDEBUG being defined on macOS through the bazel toolchain defaults. - Fix a typo and clarify Windows release config comment Original commit message: - Match macOS wd_benchmark link options with wd_binary options - Correct spelling of WIN32_LEAN_AND_MEAN - /await and /GF are ignored by clang-cl, no need to pass them in the Windows build.
fhanau
added a commit
that referenced
this pull request
Apr 23, 2024
The original PR failed to apply the `release` configuration to `release_unix`, leading to a binary size regression, especially on macOS. This was caused by bazel using fastbuild mode instead of opt mode, leading to Rust code not being optimized and -DDEBUG being defined on macOS through the bazel toolchain defaults. - Fix a typo and clarify Windows release config comment Original commit message: - Match macOS wd_benchmark link options with wd_binary options - Correct spelling of WIN32_LEAN_AND_MEAN - /await and /GF are ignored by clang-cl, no need to pass them in the Windows build.
garrettgu10
pushed a commit
that referenced
this pull request
May 13, 2024
The original PR failed to apply the `release` configuration to `release_unix`, leading to a binary size regression, especially on macOS. This was caused by bazel using fastbuild mode instead of opt mode, leading to Rust code not being optimized and -DDEBUG being defined on macOS through the bazel toolchain defaults. - Fix a typo and clarify Windows release config comment Original commit message: - Match macOS wd_benchmark link options with wd_binary options - Correct spelling of WIN32_LEAN_AND_MEAN - /await and /GF are ignored by clang-cl, no need to pass them in the Windows build.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Windows build.