fwiw, I just tried with that exact tag, same result.
Just the fact that tools/create_release.sh writes in what is
${CMAKE_CURRENT_SOURCE_DIR} while CMakeList.txt works in
${CMAKE_CURRENT_BINARY_DIR} should be reason to worry, unless they're
both the same, which shouldn't normally be the case, since build.sh
(which is called at the end of tools/create_release.sh) doesn't work
that way.Cheers, Richard In message <cadstzw4onw4qva_j6o73pyht4bevsrmu48cwpa+qkosnhkm...@mail.gmail.com> on Thu, 5 Nov 2015 16:02:47 +0100, johannes hanika <[email protected]> said: hanatos> fwiw, this used to work with the exact tag release-2.0rc1 .. hanatos> hanatos> not sure why you would want to build a release package from a different commit? hanatos> hanatos> -jo hanatos> hanatos> On Thu, Nov 5, 2015 at 2:11 PM, jeremy rosen hanatos> <[email protected]> wrote: hanatos> > ok, i'll try to look into it this WE, that's related to my new handling of hanatos> > the version string... hanatos> > hanatos> > On Thu, Nov 5, 2015 at 12:31 PM, Richard Levitte <[email protected]> hanatos> > wrote: hanatos> >> hanatos> >> Hi, hanatos> >> hanatos> >> I wanted to try my hands at building a release package from 2.0rc1, hanatos> >> and got myself in trouble. Trying tools/create_release.sh gives me hanatos> >> this configuration error: hanatos> >> hanatos> >> ... hanatos> >> -- The CXX compiler identification is GNU 5.2.1 hanatos> >> -- The C compiler identification is GNU 5.2.1 hanatos> >> -- Check for working CXX compiler: /usr/bin/c++ hanatos> >> -- Check for working CXX compiler: /usr/bin/c++ -- works hanatos> >> -- Detecting CXX compiler ABI info hanatos> >> -- Detecting CXX compiler ABI info - done hanatos> >> -- Detecting CXX compile features hanatos> >> -- Detecting CXX compile features - done hanatos> >> -- Check for working C compiler: /usr/bin/cc hanatos> >> -- Check for working C compiler: /usr/bin/cc -- works hanatos> >> -- Detecting C compiler ABI info hanatos> >> -- Detecting C compiler ABI info - done hanatos> >> -- Detecting C compile features hanatos> >> -- Detecting C compile features - done hanatos> >> -- multiarch triplet detected: x86_64-linux-gnu hanatos> >> hanatos> >> /home/levitte/gitwrk/github.com/darktable-experimental/tmp/darktable-2.0~rc1+19~g6bf271e/tools/create_version_h.sh: hanatos> >> line 27: hanatos> >> /home/levitte/gitwrk/github.com/darktable-experimental/tmp/darktable-2.0~rc1+19~g6bf271e/build/src/version_gen.h: hanatos> >> No such file or directory hanatos> >> hanatos> >> And yeah, true, at that point, there's no ./build/src... so it would hanatos> >> seem to me that this commands in the top CMakeList.txt has some hanatos> >> premature ideas of what's in the build directory: hanatos> >> hanatos> >> execute_process( COMMAND hanatos> >> ${CMAKE_CURRENT_SOURCE_DIR}/tools/create_version_h.sh hanatos> >> ${CMAKE_CURRENT_BINARY_DIR}/src/version_gen.h ${PROJECT_VERSION} hanatos> >> WORKING_DIRECTORY ${CMAKE_SOURCE_DIR} hanatos> >> ) hanatos> >> hanatos> >> And, considering tools/create_release.sh puts version_gen.sh in the hanatos> >> temporary SOURCE tree src/, not the BINARY tree one, could it be that hanatos> >> ${CMAKE_CURRENT_BINARY_DIR} in that command should really be hanatos> >> ${CMAKE_CURRENT_SOURCE_DIR}? hanatos> >> hanatos> >> Cheers, hanatos> >> Richard hanatos> >> hanatos> >> -- hanatos> >> Richard Levitte [email protected] hanatos> >> http://richard.levitte.org/ hanatos> >> hanatos> >> "Life is a tremendous celebration - and I'm invited!" hanatos> >> -- from a friend's blog, translated from Swedish hanatos> >> hanatos> >> ___________________________________________________________________________ hanatos> >> darktable developer mailing list hanatos> >> to unsubscribe send a mail to hanatos> >> [email protected] hanatos> >> hanatos> > hanatos> > hanatos> > ___________________________________________________________________________ hanatos> > darktable developer mailing list to unsubscribe send a mail to hanatos> > [email protected] ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to [email protected]
