now that the assembler language is enabled in the build system the macro
turned out to be a bit bogus and it has to handle sources control too
because some CPU specifiec sources were, previously, added unconditionally
to targets leading to build failures (especially with assembly).
CPU tests now declare variables that are cached and can be changed by the
user to avoid touching parent scope from the test macros (previously
functions for that reason).
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the custom ld.so.conf file ensures that the Katie libraries get
registered in the cache so that when installed in location other than
/usr/lib or other standard libraries path executables can operate.
Even the default libraries path (/usr/local/lib/katie) is
non-standard and requires the config, unless CMAKE_SKIP_INSTALL_RPATH
if set to ON but because RPATH is considered security issue it is
unlikely that binary distributors will turn it on when building Katie
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
on freebsd the shebang may not be correct as it, usually, places
files under /usr/local prefix instead of /usr thus calling with
what the PythonInterp cmake module has found is more reliable
cross-platform
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
