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

Investigate David Lattimore's compile speed tips #1020

Closed
1 of 3 tasks
alice-i-cecile opened this issue Feb 18, 2024 · 2 comments
Closed
1 of 3 tasks

Investigate David Lattimore's compile speed tips #1020

alice-i-cecile opened this issue Feb 18, 2024 · 2 comments

Comments

@alice-i-cecile
Copy link
Member

Article. Figure out which once work well, then update the advice to include them!

  • Faster linker: already done
  • Don't link debug info
  • Build a non-relocatable executable
@AxiomaticSemantics
Copy link

AxiomaticSemantics commented Feb 18, 2024

I often do the strip = "debuginfo" thing unless actually debugging, if anything because it massively reduces artifact sizes, would advise. I'm going to try the non-PIC build, that should indeed be a huge boon. Another thing to consider is -Zbuild-std along with the panic handler changes mentioned.

@AxiomaticSemantics
Copy link

AxiomaticSemantics commented Feb 19, 2024

The static link to musl may help some users, but various packages break in my environment, bevy_audio will not build here, didn't try further. I'd advise against the latter or a big caveat with it.

@alice-i-cecile alice-i-cecile closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants