Hi,
I wanted to try my hands at building a release package from 2.0rc1,
and got myself in trouble. Trying tools/create_release.sh gives me
this configuration error:
...
-- The CXX compiler identification is GNU 5.2.1
-- The C compiler identification is GNU 5.2.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- multiarch triplet detected: x86_64-linux-gnu
/home/levitte/gitwrk/github.com/darktable-experimental/tmp/darktable-2.0~rc1+19~g6bf271e/tools/create_version_h.sh:
line 27:
/home/levitte/gitwrk/github.com/darktable-experimental/tmp/darktable-2.0~rc1+19~g6bf271e/build/src/version_gen.h:
No such file or directory
And yeah, true, at that point, there's no ./build/src... so it would
seem to me that this commands in the top CMakeList.txt has some
premature ideas of what's in the build directory:
execute_process( COMMAND
${CMAKE_CURRENT_SOURCE_DIR}/tools/create_version_h.sh
${CMAKE_CURRENT_BINARY_DIR}/src/version_gen.h ${PROJECT_VERSION}
WORKING_DIRECTORY ${CMAKE_SOURCE_DIR}
)
And, considering tools/create_release.sh puts version_gen.sh in the
temporary SOURCE tree src/, not the BINARY tree one, could it be that
${CMAKE_CURRENT_BINARY_DIR} in that command should really be
${CMAKE_CURRENT_SOURCE_DIR}?
Cheers,
Richard
--
Richard Levitte [email protected]
http://richard.levitte.org/
"Life is a tremendous celebration - and I'm invited!"
-- from a friend's blog, translated from Swedish
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
