-
Notifications
You must be signed in to change notification settings - Fork 47
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
So. Where is "gitrevision.h"? #198
Comments
Thanks for looking to support
As you may have noticed the build system is There might be a few other issues if you are trying to mimic the complete build system. But, please get back to this issue when that happens ;-) If this is going to be an on-going story, perhaps we should change the title of this issue? |
The problem is that when CGreen is not a git repository (e.g. when a release tarball is downloaded and extracted), generated makefile at location
and hence even the make rule for generating gitrevision.h is present, it is not executed. I am not experienced with writing cmake rules, so if someone fixes it, it would be really great! |
Good point. One option would be to check for Don't see how we could generate correct git revision from a tar-ball so it'll have to be something like I'll have a look at that. In the mean time you could create one manually to avoid the problem for now. |
Thanks. 😊 |
I am thinking that in case of a release tarball, we should parse the path with some regex using Could you please point to the cmake part that generates rules for |
The CMake rules/code that generates Basically it asks There is actually an I'll have to look into why that doesn't happen. |
Turns out that there is one single word missing from
Change
to
I.e add the I'll commit this and force the 1.2.0 release to include it. |
Please check that this works in your environment. |
Hello there.
I was writing Meson support for your testing framework when I bumped into my first issue. If you can tell me where "gitrevision.h" can be located and why it was not included that would nice.
The text was updated successfully, but these errors were encountered: