Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase CMake version to > 3.9 ? #35

Closed
seriousme opened this issue Dec 6, 2018 · 5 comments
Closed

Increase CMake version to > 3.9 ? #35

seriousme opened this issue Dec 6, 2018 · 5 comments

Comments

@seriousme
Copy link

Hi,

similarly to #23 I ran into CMake version issue. LevelDB needs at least 3.9.

In the source of the installer I found the option: --skip-license
So my upgrader now consists of:

version=3.13
build=0
wget https://cmake.org/files/v$version/cmake-$version.$build-Linux-x86_64.sh 
mkdir /opt/cmake
sh cmake-$version.$build-Linux-x86_64.sh --skip-license --prefix=/opt/cmake 
ln -s /opt/cmake/bin/cmake /usr/local/bin/cmake
ln -s /opt/cmake/bin/ctest /usr/local/bin/ctest 

It works for me now but it might be convenient for others.

Cheers,
Hans

@trzecieu
Copy link
Owner

trzecieu commented Dec 7, 2018

Hi! Just bumped CMake to 3.12.2, expect to be available in ~2h once Jenkins will pick up those changes.
Cheers!

@trzecieu trzecieu closed this as completed Dec 7, 2018
@BlueSolei
Copy link

Question:

I am using the latest docker image, but I still get cmake 3.7.2, how can that be?
Here is my bash:

$ docker run -it -v $(pwd):/src -p 8000:8000 trzeci/emscripten
Unable to find image 'trzeci/emscripten:latest' locally
latest: Pulling from trzeci/emscripten
05d1a5232b46: Pull complete 
d881c9292a10: Pull complete 
cdd13bc0e0df: Pull complete 
d3707b50c53c: Pull complete 
Digest: sha256:5584393d826199360d01779af6c8da3100a64d91d706bbcb5707914ee264c21f
Status: Downloaded newer image for trzeci/emscripten:latest
root@6155b055a796:/src# cmake --version
cmake version 3.7.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

@trzecieu trzecieu reopened this Jan 5, 2019
@trzecieu
Copy link
Owner

trzecieu commented Jan 5, 2019

Indeed I can confirm this was a case.
It's fixed now:

[trzeci@app ~]$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
[trzeci@app ~]$ docker run -it --rm trzeci/emscripten:sdk-incoming-64bit cmake --version
Unable to find image 'trzeci/emscripten:sdk-incoming-64bit' locally
sdk-incoming-64bit: Pulling from trzeci/emscripten
cd8eada9c7bb: Pull complete
2d716a3fa5df: Pull complete
c4706559454a: Pull complete
407cebf2177c: Pull complete
Digest: sha256:57e6a9ae756d24224afcfaa10f26b266e8698409559b82cd46622e5194bf3633
Status: Downloaded newer image for trzeci/emscripten:sdk-incoming-64bit
cmake version 3.12.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

Sorry for inconvenience!

The problem was with Jenkins configuration and broken 1.37.17 release that prevented to re-compile incoming branch.

@trzecieu trzecieu closed this as completed Jan 5, 2019
@trzecieu
Copy link
Owner

trzecieu commented Jan 5, 2019

@BlueSolei: in addition latest tag points to the latest released Emscripten version - which is 1.38.21 (~1 month old) - I don't want to change currently pushed images unless a bug fix (some people may rely-on given tool-set).

CMake 3.12.2 is going to be a part of sdk-incoming-64bit and it will be released with 1.38.22.

If you would like to use the image locally, you can compile it with command:

git clone [email protected]:trzecieu/emscripten-docker.git
cd emscripten-docker
docker build -t emscripten  --build-arg EMSCRIPTEN_SDK=sdk-tag-1.38.21-64bit docker/trzeci/emscripten
docker run --rm -it emscripten bash -c "cmake --version && emcc --version"
cmake version 3.12.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
emcc (Emscripten gcc/clang-like replacement) 1.38.21 (commit 7a0e27441eda6cb0e3f1210e6837cae4b080ab4c)
Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)
This is free and open source software under the MIT license.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

@BlueSolei
Copy link

BlueSolei commented Jan 5, 2019

Thanks a lot for the detailed explanation.
And for this great docker image :-)
I am new to docker, so this explanation clarifies things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants