Tool/software:
Hello,
I’m seeing unexpected behavior when using the Code Composer Studio CLI to import a project. According to the documentation, the -ccs.copyIntoWorkspace option defaults to false and, when set explicitly to false, should prevent CCS from copying project files into the workspace.
However, in both macOS and Windows, project files are copied into the workspace regardless of this setting.
CCS Version: Build: 20.2.0.12__1.8.0 (under Help > About)
Platforms tested:
-
macOS Sequoia 15.5
-
Windows 10 Pro (22H2 build 19045.5965)
Command Used (macOS example):
/Applications/ti/ccs2020/ccs/ccs-server.app/Contents/MacOS/ccs-server-cli.sh \
-noSplash \
-workspace /Users/andrerc/git/thyristor_pulse_phase_control_f280013x/ti_temporary_workspace \
-application com.ti.ccs.apps.importProject \
"-ccs.location" /Users/andrerc/git/thyristor_pulse_phase_control_f280013x/epwm_ex10_chopper \
"-ccs.copyIntoWorkspace" false
Expected Behavior:
-
Project imported by reference; files should remain in their original location
-
Workspace should only contain metadata, not actual project files
Observed Behavior:
-
All project files (source, cmd files, .syscfg, etc.) are copied into the workspace directory
Here’s the resulting file tree:
➜ tree ti_temporary_workspace -L 2
ti_temporary_workspace
└── epwm_ex10_chopper
├── 28004x_generic_flash_lnk.cmd
├── 28004x_generic_ram_lnk.cmd
├── device
├── epwm_ex10_chopper.c
├── epwm_ex10_chopper.syscfg
├── targetConfigs
└── timer_interrupt.cpp
4 directories, 5 files
Troubleshooting attempts:
-
Omitting the -ccs.copyIntoWorkspace option → files still copied
-
Explicitly setting -ccs.copyIntoWorkspace false → same result
-
Verified workspace was clean before running the command
Could this be a bug in the CLI import tool, or is the documentation out of date or incorrect regarding the behavior of -ccs.copyIntoWorkspace?
Please find attached a zip file with a reproducible test case.
Any guidance or workaround would be greatly appreciated!
Thanks in advance,
André
