[Codelite-users] Multi Project Builds

[Sean F. <sea...@ri...>]

Hi,

I have lately been struggling to use CodeLite in a multi project setting on
windows. Here is my setup: I have one workspace and a few projects, which
are an executable and a few libraries, plus a few unit tests (exe). I want
to run the exe from the IDE and the unit tests as post build step.

The solution I would like to implement (ripped off from Visual Studio) is to
build all targets to a common folder under the workspace. If they happen to
be in the same repository this is kind of simple. I configure the target to
be ../$(ConfigurationName)/$(ProjectName).(exe|dll). But as it happens I am
reusing some libraries in multiple projects, so they have the their own
repositories. I would like to use as target
$(WorkspacePath)/$(ConfigurationName)/$(ProjectName).(exe|dll).

But the bad news is that the windows drive letters (c:\) look like canonical
target patterns. Actually mingw32-make.exe knows how about drive letters and
has a workaround for that. But here is the problem, the makefiles that
CodeLite writes puts the path in quotes. If the path would not be in quotes
minge32-make.exe will properly handle the path.

I think the main reason why CodeLite escapes the path is to handle potential
white spaces in the path. Honestly I would prefer that the generated
makefile has no quotes around paths and the commands that need potential
escaping should do that at the invocation level. But honestly, if you use
make and have paths with white spaces you are kind of lost anyway.

I am ready to provide a patch; but that is probably more effort than the
developers doing it... The issue here is more should the behavior be changed
or not?

Sean