Tools Question - CCS Command Line Build

If the variables are defined in a vars.ini file in the root location of the project folder, they should be automatically read in during project import. Please see this related thread.

Hello,

I just tried this, I placed the path variables file called macroWin.ini in the project root, but the paths were not updated.

When we import build variables manually we select the checkbox which says overwrite existing variables. Is there any way to force this option from the command line (or in the file).

Regards

Anuj Mitra said:

I just tried this, I placed the path variables file called macroWin.ini in the project root, but the paths were not updated.

Did you try renaming the file to vars.ini and see if that works?

Anuj Mitra said:

When we import build variables manually we select the checkbox which says overwrite existing variables. Is there any way to force this option from the command line (or in the file).

Are you using the -ccs.overwrite option? I am not sure if that overwrites existing variables though. If it does not you may have to import into a new workspace. A better long term solution may be to set the variables at the project level so they carry over with the project as needed, and don't have to be imported into the workspace each time.

AartiG said:

Did you try renaming the file to vars.ini and see if that works?

Yes, that makes no difference

AartiG said:

Are you using the -ccs.overwrite option? I am not sure if that overwrites existing variables though. If it does not you may have to import into a new workspace. A better long term solution may be to set the variables at the project level so they carry over with the project as needed, and don't have to be imported into the workspace each time.

I am importing projects into a new workspace, it's part of a process of automated builds. The project needs to work on both linux & windows platforms, so it is not possible or desirable to do this