I have a workspace where one of the build configurations is named "Release". A project in this workspace has configuration that is called "Release-32bit". So, by building workspace configuration "Release" you are building a project configuration "Release-32bit".

The same workspace has configuration called "Release-64bit" and the above mentioned project also has configuration "Release-64bit".

codelite-make has no issues building "Release-64bit" configuration but does not work with "Release-32bit". IDE build is not affected - from IDE I can build all configurations successfully. So it seems that project build configuration name should match workspace build configuration name or build fails.

I was able to workaround the issue by making workspace configuration names same with project configuration names.

Here is the command line that failed before the workaround:

codelite-make -w fplog.workspace -p spipc_test -c Release-32bit -d rebuild -e

----------Cleaning project:[ spipc_test -  ]----------
make[1]: Entering directory '/var/lib/jenkins/workspace/fplog/build_architecture/x86_32/build_target_os/Linux/codelite'
rm -f -r ./Release/
make[1]: Leaving directory '/var/lib/jenkins/workspace/fplog/build_architecture/x86_32/build_target_os/Linux/codelite'
----------Building project:[ spipc_test -  ]----------
/bin/sh: 1: spipc_test.mk: not found
Makefile:4: recipe for target 'All' failed
make: *** [All] Error 127