> On 27 Oct 2016, at 10:46, Federico Calboli <[email protected]> wrote: > > >> On 27 Oct 2016, at 10:34, Bart Janssens <[email protected]> wrote: >> >> Normally this is solved by running "cmake ." in the build directory or >> directories of the library or libraries compiled using cmake. > > Thanks! is there a way of doing it automatically and recursively until it > finds the appropiate CMakeLists.txt file so I do not have to trawl for it? > in addition, as it seems pretty simple I am surprised this does not happen > ‘automagically’.
Actually I found where to run "cmake .” and it seems to work (even if I realised that I did not fix the utf8 library…). In any case the fact I have to do by hand it is perplexing… BW F > BW > > F > >> >> Cheers, >> >> Bart >> >> On Thu, Oct 27, 2016 at 9:28 AM Federico Calboli <[email protected]> wrote: >> Hi, toady on a whim I tried >> >> make cleanall && make testall >> >> but it did not work because when julia was built cmake was at 3.6.1 and now >> it is a 3.6.2 >> >> make[2]: /usr/local/Cellar/cmake/3.6.1/bin/cmake: No such file or directory >> make[2]: *** [cmake_check_build_system] Error 1 >> make[1]: *** [/usr/local/julia/usr/lib/libmbedcrypto.dylib] Error 2 >> make: *** [julia-deps] Error 2 >> >> Now I have: >> >> ../Cellar/cmake/3.6.2/bin/cmake >> >> This problem seems extremely silly, given that it forces me *not* to upgrade >> my cmake (and maybe other software), when the make routine could do the >> equivalent of `which cmake' and use the result. >> >> Leaving this aside, is there a way of rebuilding julia with the correct >> cmake without basically removing the whole thing and rebuilding from 0? >> >> BW >> >> F > > > -- Federico Calboli [email protected]
