Unable to build mynewt 1.13.0 on Windows

[harteware07]

I recently upgraded the Version of mynewt to 1.13 and now I am unable to build anymore. Here is the console output of my build log:

Building target targets/myproject
Executing @apache-mynewt-core/boot/startup/scripts/generate_linker_script.sh

mkdir: cannot create directory ‘/link’: Permission denied
mkdir: cannot create directory ‘/link’: Permission denied
touch: cannot touch '/link/include/link_tables.ld.h': No such file or directory
touch: cannot touch '/link/include/target_config.ld.h': No such file or directory
touch: cannot touch '/link/include/memory_regions.ld.h': No such file or directory
touch: cannot touch '/link/include/bsp_config.ld.h': No such file or directory
touch: cannot touch '/link/include/mcu_config.ld.h': No such file or directory
touch: cannot touch '/link/include/user_sections.ld.h': No such file or directory
scripts/generate_linker_script.sh: line 32: /link/mynewt.ld: No such file or directory
Error: command [C:\WINDOWS\system32\bash.exe scripts/generate_linker_script.sh] exited with nonzero status 1

It seems that the variable ${MYNEWT_BUILD_GENERATED_DIR} and _PROJECT_ROOT do not exist for the generate_linker_script.sh script.

When I set the variable MYNEWT_BUILD_GENERATED_DIR in the script myself the script exits with following error:

>> newt.exe build myproject
Building target targets/myproject
Executing @apache-mynewt-core/boot/startup/scripts/generate_linker_script.sh
C:/Users/xxx/bin/targets/myproject/generated
scripts/generate_linker_script.sh: line 33: -xc: command not found
Error: command [C:\WINDOWS\system32\bash.exe scripts/generate_linker_script.sh] exited with nonzero status 127

I'm really thankful for any tips or hints on how to solve this problem.
Thanks a lot!

[sjanc]

Hi,

could you paste output of 'newt version' and 'newt info' ?

[harteware07]

Hello, thank you for your reply. Here are the two outputs: > newt.exe version Apache Newt 1.13.0 / c6bf556 / 2024-11-13_15:26 > newt.exe info Apache Newt 1.13.0 / c6bf556 / 2024-11-13_15:26 Repository info: * apache-mynewt-core: eb0ffcd, 1.13.0, (dirty: local changes) * apache-mynewt-mcumgr: 46c8ff07525ee8b52dda55ce3763fe52ba5fd013, 0.5.0 * apache-mynewt-nimble: ca67e3015eec30eb97c853112441082d709e43ba, 1.8.0 * mcuboot: 9c99326b9756dbcc35b524636d99ed5f3e6cb29b, 2.1.0 Am 07.01.2025 um 16:13 schrieb Szymon Janc:

…

Hi, could you paste output of 'newt version' and 'newt info' ? — Reply to this email directly, view it on GitHub <https://github.com/ apache/mynewt-core#3360#issuecomment-2575543131>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ AAKWDBGDDXSYEH3H5LSO2G32JPVINAVCNFSM6AAAAABUX4GXAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZVGU2DGMJTGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[kasjer]

It looks like you are working on Windows but bash.exe is taking you to WSL.
To work try running from mingw bash, Git for Windows bash should also work.

It is possible to run on WSL but then project should be inside WSL file system and then standard Linux version of commands would work for build. In this case it is still possible to have JLink installed on Windows that will be execute form Linux.

See here for installing/using mingw64 bash.

[harteware07]

Thank you so much! I changed the bash to Mingw and now it's working. After chasing down lots of build errors I finally have a working bin file. One problem is still persistent though: I cannot do partial builds. I always have to do a clean and then a complete build. If I do a partial build, I always get this error:

Error: CreateFile c\:\users\admin\git\myproj\libs\drivers\display\lvgl\include\lvgl\lv_conf.h: The filename, directory name, or volume label syntax is incorrect.

Sometimes the file name changes and it is in my SD card module. Any ideas what I could do to get partial builds to work? Thanks a lot! Am 08.01.2025 um 12:50 schrieb kasjer:

…

It looks like you are working on Windows but bash.exe is taking you to WSL. To work try running from mingw bash, *Git for Windows* bash should also work. It is possible to run on WSL but then project should be inside WSL file system and then standard Linux version of commands would work for build. In this case it is still possible to have JLink installed on Windows that will be execute form Linux. See here <https://mynewt.apache.org/latest/newt/install/ newt_windows.html> for installing/using mingw64 bash. — Reply to this email directly, view it on GitHub <https://github.com/ apache/mynewt-core#3360#issuecomment-2577483296>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ AAKWDBFFXRV2I2GGJKXHCID2JUGKFAVCNFSM6AAAAABUX4GXAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNZXGQ4DGMRZGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[kasjer]

I'm not sure which command tried to create/access lv_conf.h file.

Could you please make newt build with following options:

newt build -j 1 -p <your_target>

Run this after you have build that fails. It should do build without parallel execution and show executed commands so culprit can be found.

[kasjer]

I also see that your build tries to access lv_conf.h from strange location. I would expect lv_conf.h to be in
repos/apache-mynewt-core/hw/drivers/display/lvgl/default/lv_conf.h.

How did you specify location of this file?

[harteware07]

I started working with lvgl long time ago, when it was not included in mynewt. That's why I have my own lvgl files in my project directory. Sometimes the error also occurs on my SD card implementation. Am 15.01.2025 um 14:22 schrieb kasjer:

…

I also see that your build tries to access lv_conf.h from strange location. I would expect lv_conf.h to be in repos/apache-mynewt-core/hw/drivers/display/lvgl/default/lv_conf.h. How did you specify location of this file? — Reply to this email directly, view it on GitHub <https://github.com/ apache/mynewt-core#3360#issuecomment-2592844916>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ AAKWDBCZMUE3ZAFOKKU3XCT2KZOINAVCNFSM6AAAAABUX4GXAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJSHA2DIOJRGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[kasjer]

Ok then, you may still want to run non-parallel build to see which command wants to access file from wrong location.

[sjanc]

please reopen if this is stil an issue