-
Notifications
You must be signed in to change notification settings - Fork 272
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
Windows cmake build fails #311
Comments
Hi, Your environment does not seem to find
Suggestions:
|
A third option could be to change the CMakeLists.txt to check if the value |
I'm new to cpp and cmake so i kind of have a hard time understanding what is going on in these cmake statements. I assume GIT_VERSION is version of git that is called (but how is it used) ? I don't really understand options 2 & 3. I don't have git on my path because it is not installed, so i should probably do that first. It is not installed because i am using SourceTree as my git client, which comes with its own bundled git binaries. I guess bundling Git is quite popular for windows git clients, so it would probably a good idea to (Personally i just change hardcoded version on release with a separate commit in my projects, it helps documenting versions without being mutable like tags^^) Edit: |
GIT_VERSION is not the version of git is the version of the g3log software |
I.e. |
Oh ok, now option 2 and 3 make much more sense. I'll see what i can do. |
@Katharsas can this be closed? |
I faced a similar issue today whilst rebuilding the source from the github release tar.gz file. I solved it by just passing -DVERSION=1.3.2 to the CMake command. This bypasses the git version check and I did not see any negative outcomes. |
perfect. I just updated the doc and I consider this issue closed now: #316 |
@macdew thanks |
When i go into g3log dir and try:
cmake (latest version 3.14.1 win64) fails with
for g3log commits at tag 1.3.1, 1.3.2 and current master (9c5e7f3). When i go back to 1.3, it seems to work. This seems to be the case for both cmd and powershell.
The text was updated successfully, but these errors were encountered: