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

MacOS Support #592

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

MacOS Support #592

wants to merge 4 commits into from

Conversation

vyeevani
Copy link

@vyeevani vyeevani commented Oct 3, 2024

  • support for bazelmod
  • building wheels with bazel
  • support for macOS via not standard array_record library
  • support for ci tagging and versioning

Copy link

google-cla bot commented Oct 3, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Grain Team and others added 2 commits November 21, 2024 12:00
PiperOrigin-RevId: 698543187
- building wheels with bazel
- support for macOS via not standard array_record library
- support for ci tagging and versioning
@iindyk
Copy link
Collaborator

iindyk commented Nov 25, 2024

thanks for the PR, but it is not backwards compatible -- with this change we will lose platform tags and linux arm64 build which is required for latest NVidia GPUs. Do you think these can be added? Also, is there a way to avoid specifying requirements for every build rule?

@iindyk iindyk self-assigned this Nov 25, 2024
@vyeevani
Copy link
Author

Could you elaborate on the platform tags? I'm not entirely sure what you meant by that. On the backwards compatibility front, totally agree that it's not -- this was meant to be for me testing locally on my laptop then deploying to a cloud machine where I'd use the official grain image. If there's interest in getting this merged, I could spin on the issues that you've raised. However, if it's fundamentally incompatible with google's internal infra for cutting releases, then I'd rather just leave my fork up and sync it whenever needed.

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