nRF Connect for VSCode not showing output files when using sysbuild

I read some previous posts that there was limited support for sysbuild for the VSCode extension. There are two things that I noticed:

1. When creating a build  configuration for the nRF9151 Feather, the 'Build system default' says it uses sysbuild but when I actually do a build it uses the old build system.

2. When I change the selection specifically to `Use sysbuild` the output files no longer show up. (I know where they are but others may not!)

Parents Reply Children
  • Nice! Answers one question. Any ideas about my first question?

    1. When creating a build  configuration for the nRF9151 Feather, the 'Build system default' says it uses sysbuild but when I actually do a build it uses the old build system.

    The build still uses the non-sysbuild even though the default button says it uses sysbuild. I'm on NCS 2.7.0

  • Hi Jared, 

    Priyanka is out of the office, so I picked up this case. 

    I cannot reproduce the issue on Windows. Do you see the command with  "--sysbuild" when using the "use sysbuild" button? Try to delete the build folder and create a new build configration to see it can help or not. 

    Regards,
    Amanda H.

  • Hi Amanda

    I'm on Linux. With the default option checked I get: 

     *  Executing task: nRF Connect: Generate config circuitdojo_feather_nrf9151/nrf9151/ns for nfed/samples/test 
    
    Building test
    west build --build-dir /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test/build/circuitdojo_feather_nrf9151 /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns -- -DNCS_TOOLCHAIN_VERSION=NONE

    Versus explicitly checking sysbuild:

    west build --build-dir /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test/build_2 /home/jaredwolff/Git/nrf9160-feather-examples-and-drivers/nfed/samples/test --pristine --board circuitdojo_feather_nrf9151/nrf9151/ns --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE

    The default is not sysbuild.

  • Jared said:
    With the default option checked I get: 

    Do you mean using "build system default"?

    Jared said:
    Versus explicitly checking sysbuild:

    Do you mean using "use sysbuild"?

  • Correct. Building from scratch with the Default option does not use sysbuild. I assume the default is sysbuild since it has (sysbuild) at the top. (I think it also mentions it in the tool tip but I’m away from my machine right now)

Related