Please complete these steps and check these boxes (by putting an x inside
the brackets) _before_ filing your issue:
vim --version.:YcmDebugInfo.:YcmToggleLogs command.vim -Nu /path/to/YCM/vimrc_ycm_minimal, including what Iinstall.py (or cmake/make/ninja) including its invocationThank you for adhering to this process! It ensures your issue is resolved
quickly and that neither your nor our time is needlessly wasted.
On our HPC cluster, we feature multiple toolchains (GCC 4.8.5, 6.3.0, 8.2.0) mapped to C++ standards (11, 14, 17). I got a request from a cluster users to install the requirements needed for YouCompleteMe. This users and his institute are heavily using the GCC 6.3.0 toolchain and have all their software setup for this particular toolchain.
I would like to prevent that the users have to install all their software for GCC 8.2.0 (this will happen, but rather in the future). I thought that looking for an older version of YouCompleteMe that is only requiring C++14 support would solve this conflict.
When looking at the YouCompleteMe github repository, I noticed that this software does not have a versioning beyond git commits (no releases, no tags). How can I find out which is the last commit, before the code was changed according to the C++17 standard?
Any help is appreciated. Thank you in advance
Sam
I have pushed a branch legacy-c++11 to the main repo, which can be checked out:
cd /path/to/YouCompleteMegit fetch origingit checkout legacy-c++11git submodule update --init --recursive./install.py .... usual arguments...For people using plugin managers, see your plugin manager documentation for how to set a branch to checkout.
Let me know if that works for you and I'll drop a note in the readme.
ta
Ben
@puremourning Thank you for your fast answer and for pushing a legacy branch of YouCompleteMe. This should resolve the issue. Today I am fully booked with appointments, but tomorrow I will try to compile the software myself and then provide you some feedback if it worked. Again, thank you for your help.
Compiling with GCC 6.3.0 worked perfectly fine. Thank you again for your help
Most helpful comment
I have pushed a branch
legacy-c++11to the main repo, which can be checked out:cd /path/to/YouCompleteMegit fetch origingit checkout legacy-c++11git submodule update --init --recursive./install.py .... usual arguments...For people using plugin managers, see your plugin manager documentation for how to set a branch to checkout.
Let me know if that works for you and I'll drop a note in the readme.
ta
Ben