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.

ccs5.1: How to use relative path filenames in Lauch Configurations

Other Parts Discussed in Thread: SYSBIOS

Hi,

I have prepared some Lauch Configurations (Debug Configurations), which work well basically.

Just for the purpose of checking them into a version control system I would like to avoid absolute file path names for e.g program name.

I made some experiements with using variables, but I wasn't successfull. It seems that variables nor relative path names are allows for file name references here.

Does anybody know about how to use relative path or variable names in LauchConfigurations ?

regards

Alois

  • Alois,

    I am not sure if this is what you are looking for, but I will give it a shot:

    In the screenshot you sent, if you select a project from your workspace the Program option is filled with a path relative to the selected project:

    ${build_artifact:image_processing_evmc6678l_master.out}

    Also, in the main tab, if you have a target configuration file (.ccxml) in your project, you can point to it using a specific variable:

    ${workspace_loc}/image_processing_evmc6678l_master/<name_of_the_target_configuration_file.ccxml>

    Keep in mind that both approaches take into consideration that the project is in the workspace. I haven't used such variables when a project is in an arbitrary location in the filesystem.

    Hope this helps,

    Rafael

  • Do you know of a place where those internal variables are documented?  I've searched your website, this forum, and various Eclipse and RTSC sites and couldn't find anything.

    I'm not hijacked this thread, mind you.  I had a similar question.  Specifically, for ${build_artifact}, what are all the qualifiers can be used?  More specifically, is there a way to cite the build artifact of a specific profile/configuration?  For instance, say I have an application that I am loading on two different DSPs.  On one I want to load the Debug build and the other I want to load the Release build.  I know it can be done just by citing the specific out file explicitly, but is there any way to do generically by profile name?

  • Hi Rafael,

    so far your path proposals are working in my setup.

    As my project is not located in the workspace path, I used a slightly modified version:

    ${workspace_loc:/image_processing_evmc6678l_master/TargetConfiguration-EVM6678-bh-xds560v2-lan.ccxml}

    For the program the correct string is

    ${build_artifact:image_processing_evmc6678l_master}

    instead

     

    ${build_artifact:image_processing_evmc6678l_master.out}

     

    Could you point me to a description of those variables? I found  the external tools variables at the ccs help page (same on the eclipse page):

    http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.platform.doc.user/concepts/concepts-exttools.htm

    But still I cant find 'build_artifact' actually.

     

    regards

    Alois

     

  • Alex said:
    Specifically, for ${build_artifact}, what are all the qualifiers can be used?  More specifically, is there a way to cite the build artifact of a specific profile/configuration? 

    the usage is ${build_artifact:<project_name>}. It will automatically use the configuration that is currently active for the specified project. This cannot be controlled (i.e. you cannot tell it to explicitly use a specific configuration)

    Thanks

    ki

  • Hi everyone,

    Just adding to the discussion, I usually right-click on the project and inspect the value of the build variables, as several of them are dynamic and heavily dependent on the CCS installation and project in focus.

     

    If using a CCS Project, go to CCS Build --> tab Build Variables. While several variables are directly shown on this view (check the CG_TOOL_ROOT in the attached picture), others marked as <ECLIPSE DYNAMIC VARIABLE> are only displayed when double-clicking on it (the COM_TI_SDO_GRACE_INSTALL_DIR).

    If using a GCC Project, go to C/C++ Build --> Build Variables

    To see the system environment variables used by Eclipse, check the menu Window --> Preferences --> C/C++ --> Build --> Build Variables. This is useful to verify if an environment variable is being properly recognized by the IDE.

    Alois, thanks for the correction of the variable.

    Regards,

    Rafael

     

  • Hi Rafel,

    thanks for the details on variables.

    Just in case of <ECLIPSE DYNAMIC VARIABLE> entries, may installation does not display any values. I double-click a variable with <ECLIPSE DYNAMIC VARIABLE>, e.g.  COM_TI_RTSC_SYSBIOS_INSTALL_DIR, and an empty Value field is displayed. I would expect to see an actual value, as in your example.

    I tried several variables, seems to be a general issue.

    Any suggestion ?

    regards

    Alois