TMS320F2811: TMS320F2811

Hello

Could you please try to check project preferences?

Maybe "Use default build command" is unchecked?

Hello Disona,

Thank you for the quick reply.

"Use default build command" is checked in the project. I can see that gmake is called when the project is built using the CCS GUI.

The statement "make all"  is displayed when I try to build the same project using the command line.

I guess I should add that I would rather use gmake because it is provided as part of CCS.

Hello Ashley,

The same make utility should be used when building from the command-line.

Can you post all the build output in the console from your command-line build?

Thanks

ki

Hello Ki,

Here is the output from my console. Some of the folder names have been removed for posting. As stated earlier, I do not have make.exe installed on this machine.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Tue Jun 08 11:38:24 EDT 2021]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...

================================================================================
Building...

11:38:31 **** Build of configuration Debug for project Controller_Build ****
make all
Cannot run program "make": Launching failed

Error: Program "make" not found in PATH
PATH=[C:/ti/ccs920/ccs/eclipse/jre/bin/server;C:/ti/ccs920/ccs/eclipse/jre/bin;C:/ti/ccs920/ccs/eclipse/jre/lib/amd64;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;]

11:38:32 Build Failed. 1 errors, 0 warnings. (took 330ms)

================================================================================
CCS headless build complete! 1 out of 1 projects have errors.

Are you running from a DOS command window? Or PowerShell? If it is the latter (PowerShell), can you try the former?

Can you also post the exact command being used to build the project?

I am running from a DOS command window. I opened the window like this.

I am calling build.cmd within the window. The contents of build.cmd is:

@echo off

REM Run the Debug build procedure
C:\ti\ccs920\ccs\eclipse\eclipsec -noSplash -data "%cd%" -application com.ti.ccstudio.apps.projectBuild -ccs.buildType full -ccs.projects Controller_Build -ccs.autoImport -ccs.configuration Debug

can you echo on and then provide the full console output again? I would like to see how the command is actually executed.

Here is the console output.

S:\Engineering\Software>REM Run the Debug build procedure

S:\Engineering\Software>C:\ti\ccs920\ccs\eclipse\eclipsec -noSplash -data "S:\Engineering\Software" -application com.ti.ccstudio.apps.projectBuild -ccs.buildType full -ccs.projects Controller_Build -ccs.autoImport -ccs.configuration Debug

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Tue Jun 08 13:07:39 EDT 2021]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...

================================================================================
Building...

13:07:53 **** Build of configuration Debug for project Controller_Build ****
make all
Cannot run program "make": Launching failed

Error: Program "make" not found in PATH
PATH=[C:/ti/ccs920/ccs/eclipse/jre/bin/server;C:/ti/ccs920/ccs/eclipse/jre/bin;C:/ti/ccs920/ccs/eclipse/jre/lib/amd64;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;]

13:07:54 Build Failed. 1 errors, 0 warnings. (took 435ms)

================================================================================
CCS headless build complete! 1 out of 1 projects have errors.

Hello Ki,

I have experimented with a script where if I first import the project and include the -ccs.autoBuild option, the build procedure runs as expected, invoking gmake like it does in the GUI instead of running make.

REM Try importing the project first.
C:\ti\ccs920\ccs\eclipse\eclipsec -noSplash -data "%cd%" -application com.ti.ccstudio.apps.projectImport -ccs.location Controller_Build -ccs.overwrite -ccs.autoBuild

REM Run the Debug build procedure
C:\ti\ccs920\ccs\eclipse\eclipsec -noSplash -data "%cd%" -application com.ti.ccstudio.apps.projectBuild -ccs.buildType full -ccs.projects Controller_Build -ccs.autoImport -ccs.configuration Debug

The partial output is as follows:

--------------------------------------------------------------------------------
Importing project from 'S:/Engineering/Software/Controller_Build'...

Done!

**** Build of configuration Debug for project Controller_Build ****

"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 4 all -O

and then the following...

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Tue Jun 08 14:52:14 EDT 2021]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...

================================================================================
Building...

**** Clean-only build of configuration Debug for project Controller_Build ****

"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 4 clean -O

.
. (Sorry I can't post the entire message)
.
Finished clean

**** Build Finished ****

**** Build of configuration Debug for project Controller_Build ****

"C:\\ti\\ccs920\\ccs\\utils\\bin\\gmake" -k -j 4 all -O

.

. (Sorry I can't post the entire message)

.

Importing the project first appears to avoid the make.exe problem although I don't know why.

Ashley Scott said:

I have experimented with a script where if I first import the project and include the -ccs.autoBuild option,

Ah ok. I didn't realize that the project was not imported to the workspace.

Actually, I've been experimenting and realized the following: that the issue occurs with clean workspaces that were never used before (no .metadata folder). If you try running the projectBuild command with a clean worksapce, it will fail with the error you mentioned. But in the meantime, I see that the .metadata folder in the workspace was created. Then if I run the same exact command again, it works! I looks like you need to run the projectImport command to import the project first if you are using a clean workspace. If it is not a new workspace location, the you can run the projectBuild command with autoImport.

I'm not sure if this is by design, but this is the behavior I see which aligns with your observations. I'll get confirmation if this is intended behavior or a bug.

Thanks

ki