-
Notifications
You must be signed in to change notification settings - Fork 15
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
CMake Error: Unable to read VERSION file #94
Comments
Solution:Include a project devs/maintainers please let me know if you are also encountering this issue and we can include the Thanks |
EdgeX community normally use semver branch to retrieve the version number |
Do you mean to say we need to do it manually referring to semver branch when we could you please explain if this is an issue or it doesn't need any improvements ? |
no, I mean the build script should be able to retrieve the version number and generate the VERSION file Line 26 in ca615f7
we wrote this logic in the Makefile please try to use make build or make docker instead of executing the build.sh directly
|
Using make build does eliminate the error ! I'm not sure why ./scripts/build.sh is causing CMake Error at CMakeLists.txt:61 (FILE):
FILE STRINGS file
"/home/mpunix/edgex-foundry/edgex-device-sdk-c/device-bacnet-c/src/c/../../VERSION"
cannot be read. Please feel free to close, or we could improve bacnet README.md |
Makefile generate the VERSINO file and execute build.sh |
all the repository use feel free to open a PR to modify the README |
🐞 Bug Report
Affected Services [REQUIRED]
https://github.com/edgexfoundry/device-bacnet-c.git
device-bacnet-c is affected due to cmake error while executing
./scripts/build.sh
Is this a regression?
Currently I'm facing this error when cloning v3.1.0 & v3.0.1 ( I have not checked other versions )
Description and Minimal Reproduction [REQUIRED]
./scripts/build.sh
🔥 Exception or Error
Error snippet:
Full Error logs:
🌍 Your Environment
Deployment Environment: Ubuntu 22.04
EdgeX Version [REQUIRED]: 3.1.1 - Napa
The text was updated successfully, but these errors were encountered: