Avoid potential FTBFS in tde_setup_gcc_visibility #24
Fusionado
SlavekB
fusionados 1 commits de feat/setup-gcc-visibility-kdemacros
en master
hace 5 años
Cargando…
Referencia en una nueva incidencia
Aún no existe contenido.
Eliminar la rama con el nombre 'feat/setup-gcc-visibility-kdemacros'
Eliminar una rama es permanente. NO PUEDE deshacerse. ¿Continuar?
If a user builds in an environment that is not clean, while building dependencies that do not need tdelibs, the previously installed tdelibs can be searched for and gcc visibility tested. In that case, kdemacros.h that is not on CMAKE_INCLUDE_DIRS, can lead to a test failure. Therefore, the full path to the detected kdemacros.h is now used.
If a user builds in an environment that is not clean, and the module that is currently being built does not use TDE and / or TQt but these are found on the disk, they are tested on GCC visibility, which is unwanted and misleading. Therefore, tests are now conditioned by whether the module has already detected TDE and / or TQt.
LGTM
f8254e1561
.