All you need to know in one place.
Table of contents:
All you need to know in one place.
Table of contents:
| #!/bin/zsh | |
| # Grab PROJECT from Cargo.toml project.name | |
| PROJECT=$(grep "name" Cargo.toml | cut -d '"' -f 2 | head -n 1) | |
| PROJECT_ORG="bevyengine" | |
| PROJECT_ORG_STRUCTURE="org.${PROJECT_ORG}.${PROJECT}" | |
| BEVY_RELEASE="refs/heads/release-0.15.2" | |
| echo "Creating new Bevy project: ${PROJECT} with organization structure: ${PROJECT_ORG_STRUCTURE}" |
The JaCoCo results from all subprojects shall be combined.
main, but it might not.pdfdoclet.sh setting correctlyPATH: the Java bin pathDOCLET_PATH: the path to the downloaded PDFDoclet JARSRC: the path to your source code containing the JavaDocPACKAGES: the list of all the packages in your source codeOUTPUT_NAME: optionally, the output name of the generated pdf (the directory must exists).pdfdoclet.config changing api.title (the title of the first page of the JavaDoc) and api.author (your name)One machine, several git identities: typically personal vs work, GitHub vs GitLab, or two accounts on the same provider. This setup makes every repository pick the right name, email, and keys on its own, so no work commit ever goes out under your personal address (or the reverse). In a hurry: run the Appendix B script once per identity.
Using perf:
$ perf record -g binary
$ perf script | stackcollapse-perf.pl | rust-unmangle | flamegraph.pl > flame.svg
NOTE: See @GabrielMajeri's comments below about the
-goption.