Closed erlingrj closed 2 days ago
The issue seems to be with the loading of the VERSION file which is to be found in at ZEPHYR_BASE/VERSION. It appears to be confused by the folder named version in the current directory.
Well no having a VERSION file in an application is actually a supported feature too. I've never heard of such a thing on an os creating a version
folder and no-one else has reported such an issue and there's plenty of mac users, can you explain how this version
folder is created, and assume you have a case insensitive option enabled on your OS since the default filesystem in mac is case sensitive?
Well no having a VERSION file in an application is actually a supported feature too. I've never heard of such a thing on an os creating a
version
folder and no-one else has reported such an issue and there's plenty of mac users, can you explain how thisversion
folder is created, and assume you have a case insensitive option enabled on your OS since the default filesystem in mac is case sensitive?
Hi and thanks for your reply. It is not the OS that creates the directory named version
it is part of an application that I am porting to Zephyr and I rather not change it. It appears the default file system on macOS is not case-sensitive, which explains why I am not seeing this problem on Ubuntu.
Would it be possibly for the build-system to differentiate between a file named version
and a directory named version
?
Have had a look and no, this is not possible. The cmake code can be changed but the file is also sourced by Kconfig, so the only option is to rename your folder, sorry
OK, thanks for your help!
Describe the bug If a folder named
version
is located at the root of a project, various CMake errors will arise.To Reproduce
The issue seems to be with the loading of the VERSION file which is to be found in at ZEPHYR_BASE/VERSION. It appears to be confused by the folder named version in the current directory.
Logs and console output
Environment (please complete the following information):
Additional context