-
-
Notifications
You must be signed in to change notification settings - Fork 611
Notes About ccache
sommermorgentraum edited this page Oct 17, 2024
·
3 revisions
ccache is a nice tool, but we certainly realized some issue of its behavior in this project, that could waste your time instead of save your time. So it's default off now, unless you manually enable it.
Just keep in mind that these issues could be made:
- When you compiled with ccache enabled, and use git to merge/pull new changes, it can only detect a part of your change, and would compile fail. It cannot be fixed by
make clean
, you hvae to delete the build dir and start over. - Sometimes ccache cause linking stage took extremely long.
- Unknown linking error until you
make clean
and start over again.
If you are aware of these issue and you are sure you are able to realized them, when they appear, follow this to enable ccache:
#(...other steps that in compile guide...)
mkdir build
cd build
cmake -DUSE_CCACHE=ON ..
make -j
#(...other steps that in compile guide...)
#(...other steps that in compile guide...)
mkdir build
cd build
cmake -DUSE_CCACHE=OFF ..
make -j
#(...other steps that in compile guide...)
#(...other steps that in compile guide...)
mkdir build
cd build
cmake ..
make -j
#(...other steps that in compile guide...)
#(...other steps that in compile guide...)
mkdir build
cd build
cmake -G Ninja -DUSE_CCACHE=ON ..
ninja
#(...other steps that in compile guide...)
#(...other steps that in compile guide...)
mkdir build
cd build
cmake -G Ninja -DUSE_CCACHE=OFF ..
ninja
#(...other steps that in compile guide...)
#(...other steps that in compile guide...)
mkdir build
cd build
cmake -G Ninja ..
ninja
#(...other steps that in compile guide...)
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.
How to collaborate
How to ask questions correctly
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- User interface
- Powering the PortaPack
-
Troubleshooting
- Won't boot
- Config Menu
- Firmware upgrade
- Diagnose firmware update in Windows
- Receive Quality Issues
- No TX/RX
- TX Carrier Only
- H2+ speaker modifications
- Dead Coin Cell Battery
- Factory Defaults
- SD card not recognized by PC with the SD-card over USB selected
- DFU overlay
- Full reset
- SolveBoard
- How to Format SDCard
- Applications
-
Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi)
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes