Troubleshoot list#
If neither of these suggestions helped and you think you encountered an AUI's issue, consider reporting it on GitHub.
Linking problems#
- Make sure you are using
aui_link
instead oftarget_link_libraries
at least for AUI's components. -
Try using static build instead of shared libraries.
Assets#
See also: AUI Assets
- Ensure you have called
aui_compile_assets()
in yourCMakeLists.txt
. - Make sure you are using
aui_link
instead oftarget_link_libraries
at least for AUI's components. - If you are
aui_link
'ing asset-containing modules (i.e.aui::views
) against static library, consider link them also with the final executable (PUBLIC
linking does not solve this issue on Linux). - Try using WHOLEARCHIVE flag.
Build cache invalidation#
Symptoms:
- Linking problems
- Newly added/removed files not being recognized by the build system
- Changes in CMake scripts are not "visible" in IDE
- Other weird issues
Cache invalidation is one of the software engineering problems (along with naming). There's cheatsheet on how to invalidate caches:
- Reload CMake cache
- In CLion: File > Reload CMake Project
- In Visual Studio Code:
F1
>CMake: Configure
- In CLI: or
- Delete
CMakeCache.txt
from your CMake binary dir (cmake-build-debug
orcmake-build-release
in CLion). - Delete your CMake binary dir.
- Change AUI version (also may need
CMakeCache.txt
to be deleted) - Delete aui.boot cache dir (~/.aui (AUI.Boot Cache Dir) unless otherwise specified)