ahmidou
commented
6 years ago Hi, I successfully compiled cling on on the same config as you. in gitbash: git clone http://root.cern.ch/git/llvm.git src cd src git checkout cling-patches cd tools git clone http://root.cern.ch/git/cling.git git clone http://root.cern.ch/git/clang.git cd clang git checkout cling-patches cd ../..
mkdir build cd build REM cmake -DCMAKE_INSTALL_PREFIX=[Install Path] -DCMAKE_BUILD_TYPE=[Build configuration, e.g. Release or Debug] ..\src cmake -DCMAKE_INSTALL_PREFIX=C:/WORK/CLING -DCMAKE_BUILD_TYPE=Release -G "Visual Studio 15 2017 Win64" C:/WORK/CLING/src cmake --build . cmake --build . --target install
I hope this help!
konstantint
danhambleton
Zmote
liudonghua123
bellenot
iammosespaulr
joao-aguirre
uncle-betty
One rainy Wednesday evening I was looking for procrastination options and I found them in the form of setting up Cling. Let me tell you this story, hoping it may be useful to either someone planning to repeat this or to work on improving this process.
I started by searching precompiled Windows binaries. For some reason (why?) the official are not available, but I found the Anaconda cling package. So I tried installing it first:
conda create -n cling clingAfter the download was complete I found the
clingbinaries underAnaconda3\envs\cling\Library\bin, howevercling.exethrew a bunch of warnings and crashed on any nontrivial command. OK, why not compile Cling myself, right? The night was young.git clone https://github.com/root-project/cling.gitcd cling\tools\packagingRead the README, figure out I need Python 2, OK.
conda create -n py27 python=2.7.13activatepython cpt.py -cThe program prints one error about not being able to read some registry key, but otherwise looks happy. Well, let's try building. Yes, I know it is written you need VS2012 but I only have 2017. Perhaps it will work?
python cpt.py --last-stable=pkgThe program starts preparing the environment and at some point attempts to download CMake. The download succeeds but then some exception is thrown on copying CMake. I look in the code. It turns out the
cmakeDirvariable is used but never declared."Well, why don't I install CMake normally, I need it anyway, and if I have it installed the code won't even reach the place with
cmakeDir". So I go to cmake.org, install CMake using the latest installer, and try again:python cpt.py --last-stable=pkgNope, the program does not care about my newly installed cmake and still wants to download one of its own crashing on
cmakeDirafterwards. I check thatcmakeis in the path, doset CMAKE=....just in case. No help. After studying the code a bit more I see that that there's a line which checks CMake version as follows:vers = [int(v) for v in rslt.split()[2].split('.')]This assumes that the version is consisting of three dot-separated integers, whilst my CMake has version
3.10.0-rc1. Whatever, let's just comment that (and the following) line out and try again!python cpt.py --last-stable=pkgNow everything looks fine. CMake configures the project, a long-ish build starts, but fails with some message about an undefined identifier. Googling the error tells me I should not be building with VS2017, but VS2015 could work. Luckily I have the VS2015 build toolchain installed with VS2017 so I only need to let CMake know to use that one by passing the
-G "Visual Studio 14 2015 Win64"parameter.After some failed attempts to pass it using
--with-cmake-flags(apparently I'm not good at escaping quotes) I simply hard-code it incpt.py(I've messed around already, so who cares, right?):EXTRA_CMAKE_FLAGS = args.get('with_cmake_flags') + ' -G "Visual Studio 14 2015 Win64"'Delete everything under
c:\ci\build\builddir.python cpt.py --last-stable=pkgBad luck. Now CMake cannot configure the project for some reason. After an hour or so of googling, I find out VC2017 comes with broken VC2015 build tools, and further hacks need to be done to fix this:
vcvarsall.bat.VCTargetsPathvariable.vcvarsall.bat.Fine, on we go!
python cpt.py --last-stable=pkgNow the build fails because of the line
#error "Unsupported/Untested _MSC_VER"somewhere inPlatformWin.cpp. Well, we're fine with untested, so let's comment this out.python cpt.py --last-stable=pkgYay, the build step passes now. The
installfails. It turns out that in order to copy the correct files to make the package,cpt.pylooks for the filedist-files.txtunderc:/ci/build/cling-src/tools/cling/tools/packaging. There's onlydist-files.json, however. Luckily, thedist-files.txtis available in my current directory (the one where I checked cling out), so I just copy it toc:/ci/build/....python cpt.py --last-stable=pkgOK, now the build and install steps pass, the
teststep fails. The reason seems to be the lack ofcatcommand (presumably this would not be a problem if I had MSYS Git set up, but I really don't want to screw my current Git). I havecatincygwin, so let's try this way:set PATH=%PATH%;C:\cygwin64\binpython cpt.py --last-stable=pkgNow I have 16 failing tests, but 98 are passing, so perhaps the failing ones are not that crucial (I won't be using Cling in production). Let's go on. Apparently I need to disable the test step to proceed, though:
python cpt.py --last-stable=pkg --no-testNext problem comes up in the
make_nsistep:UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 166: ordinal not in range(128)Hmmm... The only non-ASCII symbol in the whole file is ©. Let's replace it with (c) and try again.
python cpt.py --last-stable=pkg --no-testNew milestone:
WindowsError: [Error 2] The system cannot find the file specified. However, at this point I actually saw all the necessary files being copied toc:\Windows\Temp\cling-obj, so perhaps I could go check out how these worked out.cd C:\Windows\Temp\cling-obj\bincling.exeJust like in the Anaconda distribution, I get a bunch of warnings and the shell crashes on any input (except variable declarations and assignments).
At this point I gave up. Apparently it's easier to run cling in a docker container at the moment. But maybe I missed some very easy shortcut along the way?