This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Multiple target configurations and build configurations doesn't have a relative path

Hello,

Sorry for the horrible title for this issue, but that's the best i could explain in such a short space.


I have a project with 2 build configurations and 2 different targets that are supposed to be running in parallel and I want to debug them simultaneously. Whenever I open the debug configurations and put the fixed path to each .out file in the "Program" field located in the "Program" tab  the debugging process works perfectly. The thing is that I want to put this in a repository, so this file path cannot be fixed to my PC, it must have a relative path.


I tried using ${build_artifact:projectName}, since I read somewhere that this path changes depending on the build configuration it is configured for. Meaning that it should load the file located in the "build1/projname/projname.out" on the first microcontroller and then it should load the file located in "build2/projname/projname.out".

This doesn't happen. It loads only one build configuration into both microcontrollers (the first configuration). Could anyone help me?

This is my target configuration file:

And this is my debug configuration:

  • Hi Pablo,

    I assume you have one project with two build configurations.

    Pablo Cottens said:
    I tried using ${build_artifact:projectName}, since I read somewhere that this path changes depending on the build configuration it is configured for.

    Actually, that variable will always apply to the active build configuration subfolder of the project

    Pablo Cottens said:
    Meaning that it should load the file located in the "build1/projname/projname.out" on the first microcontroller and then it should load the file located in "build2/projname/projname.out".

    Since can only be one active build configuration for a project, it would reference the same out file for both cores.

    Pablo Cottens said:
    It loads only one build configuration into both microcontrollers (the first configuration)

    If the first build configuration is the active build configuration, then this is actually the intended behavior.

    Thanks

    ki

  • Yes, you are right in assuming the the build configurations are in the same project. 

    What I want to know, is there a way to load each out file (generated by both build configurations) into the correct microcontroller using a relative path? What I'm doing right now is adding the file path using the "workspace" button ... but it inserts a fixed path. Since this project is going into a repository I really need to know if there is a way to do this without using fixed paths:

    for example:

    ${build_conf_1_out_folder:projName}

    ${build_conf_2_out_folder:projName}