Single Build folder with ncs 2.0.0, naming is different

[nRF5xFanboy]

Hi All,

I am migrating some applications (each with multiple custom board) from nCS1.5.1 + nCS1.9.1 to nCS2.0.0

I also noticed that in nCS2.0.0 the build output folder is named different , compared to nCS1.9.1

When you have multiple custom boards stm32 + nrf52x and use MS visualCode and ncs 1.9.1 and build the same application

For example:
the build folder is named "build_custom_stm32F411" for the custom board based upon the stm32F411
the build folder is named "build_custom_nrf52840dk" for the custom board based upon the Nordic 52840

Conclusion:
Support multiple build / board configuration is very handy when building for multiple boards

unfortunately for nCS 2.0.0 this is now changed/ different 

When you have a custom board X and use MS visualCode and ncs 2.0.0 to the build,
the result is in folder "build for the board X 
Conclusion:
It is not so handy when building output are coming into the same application for multiple boards.

Any idea / hint / tip how to fix this correctly.

Thanks in advance ...

[Marte Myrvold]

Hi,

You can name the build directory whatever you want, regardless of board or anything else, using the "Build directory name" in VS Code:

Best regards,

Marte

[nRF5xFanboy]

Hello Marte,

OK thanks for your answer.

I am aware this was my mistake, caused by my the transition from SES to VScode.

This folder naming was always done by Segger Embedded Studio
which append the board to the build folder name (a useful feature) when working with multiple boards.

This is not a feature in VSCode, so now I aware that I must do some manual steps when building for multiple boards.

Best regards,
    nRF5xFanBoy

PS. this ticket can be closed.