Fixes#550: on fresh install with version 3.9.1, the line in lapacke-config.cmake is:
set(LAPACK_DIR "${_LAPACKE_PREFIX}/lib/cmake/-3.9.1")
And it should be:
set(LAPACK_DIR "${_LAPACKE_PREFIX}/lib/cmake/lapack-3.9.1")
Similarly to the previous commit, this commit abstracts the detailed list
of libraries associated with LAPACKE and streamlines the configuration
of user projects. They can now simply specify ${LAPACKE_LIBRARIES}
independently of the LAPACKE and LAPACK build options.
Co-authored-by: Pablo Hernandez <pablo.hernandez@kitware.com>
This is mostly a long term maintenance improvement.
Many coding styles require elimination of trailing whitespace, and
many editors and source code management configurations automatically
gobble up whitespace. When these tools gobble up whitespace, it
complicates reviewing the meaningful code changes.
By removing whitespace on one patch, it makes future
code reviews much easier.
=SCRIPT====================================================================
if which tempfile &>/dev/null; then
TEMPMAKER=tempfile
elif which mktemp &>/dev/null; then
TEMPMAKER=mktemp
else
echo "Cannot find tempfile program." 2>&1
exit 1
fi
MYTEMP=$($TEMPMAKER)
trap 'rm -f $MYTEMP' SIGINT SIGTERM
stripit() {
echo "stripping $1"
sed 's/[ \t]*$//' "$1" > $MYTEMP
cp $MYTEMP "$1"
}
if [ $# -gt 0 ]; then
while [ "$1" != "" ]; do
stripit $1
shift
done
else
while read -t 2; do
stripit $REPLY
done
fi
rm $MYTEMP
=================================================
CMake Error at src/lapack-install/lib64/cmake/lapacke-3.6.1/lapacke-config.cmake:13 (include):
include could not find load file:
src/lapack-install/lib64/cmake/lapacke-3.6.1/lapacke-targets.cmake
Call Stack (most recent call first):
CMakeLists.txt:26 (find_package)
-- src/lapack-install/lib64/cmake/lapacke-3.6.1
-- Configuring incomplete, errors occurred!
See also "src/lapackTest-bld/CMakeFiles/CMakeOutput.log".
The file was installed in:
src/lapack-install/lib/cmake/lapacke-3.6.1/lapacke-targets.cmake
^^ - Missing lib suffix of 64
During building of external packages, only the build tree or install
tree files should be used (the source tree may not be available from
the binary package). Set to use the build tree locations for the
configuration files.
chayleaf