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 env var for specifying custom BDWGC path #108

Merged
merged 3 commits into from
Jan 18, 2024

Conversation

jacob-hughes
Copy link
Collaborator

No description provided.

@@ -5,8 +5,8 @@ use std::process::Command;

const BOEHM_REPO: &str = "https://github.com/softdevteam/bdwgc.git";
const BOEHM_ATOMICS_REPO: &str = "https://github.com/ivmai/libatomic_ops.git";
const BOEHM_DIR: &str = "bdwgc";
const BUILD_DIR: &str = "lib";
const BOEHM_DEFAULT_SRC_DIR: &str = "bdwgc";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we consistently call this BDWGC (including the env var etc)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think so really yeah. I'll push an update.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this PR is really just a bunch of miscellaneous fixes, I've decided to go ahead and fix this across the entire codebase: 6cfff56

@ltratt
Copy link
Member

ltratt commented Jan 18, 2024

Do you want to squash?

@jacob-hughes
Copy link
Collaborator Author

No, I think these commits should be separate. If you're ok with that, this is ready to merge.

@ltratt ltratt added this pull request to the merge queue Jan 18, 2024
Merged via the queue into softdevteam:master with commit 2a214a6 Jan 18, 2024
2 checks passed
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.

2 participants