Skip to content

Conversation

@normanmaurer
Copy link
Member

Motivation:

We should support m1 as more and more users are switching to it.

Modifications:

  • Add profile for boringssl-static to cross compile for m1
  • Adjust finish release script to also include m1

Result:

Mac M1 is supported

Motivation:

We should support m1 as more and more users are switching to it.

Modifications:

- Add profile for boringssl-static to cross compile for m1
- Adjust finish release script to also include m1

Result:

Mac M1 is supported
@hyperxpro
Copy link
Contributor

Does compiling require an actual M1 chipset? I mean, will you be manually compiling binary on your M1 machine?

@normanmaurer
Copy link
Member Author

@hyperxpro no its cross-compiling on intel.

@normanmaurer normanmaurer added this to the 2.0.42.Final milestone Sep 8, 2021
<osxCrossCompile>true</osxCrossCompile>
<macOsxDeploymentTarget/>
<cmakeOsxDeploymentTarget/>
<cflags>-target arm64-apple-macos11 -Werror -fno-omit-frame-pointer -fvisibility=hidden -Wunused -Wno-unused-value -O3</cflags>
Copy link
Member

Choose a reason for hiding this comment

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

Not in this PR, but at some point I think it would be good to have -Werror be controlled by a property, so people can turn it off if they have a different compiler or compiler version.

@normanmaurer normanmaurer merged commit 7280707 into main Sep 8, 2021
jakub-id added a commit to folio-org/okapi that referenced this pull request Nov 24, 2021
Which includes updated netty and netty-tcnative with M1 support,
see netty/netty-tcnative#662
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.

3 participants