[CMake] KDevelop3 and Build->Compile file

[David Somers]

On Wednesday 20 July 2005 19:17, Filipe Sousa wrote:
> On Wednesday 20 July 2005 17:58, David Somers wrote:
> > There is a problem somewhere with the way that cmake makes the kdevelop3
> > project files.
> >
> > Example. With a project made by KDevelop3, when I do Build->Compile file,
> > the messages are:
>
> You can't use Build->Compile. When you do that kdevelop run make
> source_file or make source_file.o. You are not using any Makefile. That's
> the default behavior of make. If you do:
[snip]
> The right way is Build->Build Project

A work-around to the limits of Build->Compile is in Project->Project 
Options->Build Options->Make ... simply add -w to Additional make options (so 
then there is the right things output so next/previous error works.)

It might be a good idea to have -w set when cmake generates the KDevelop3 
project files.

Sure, this may not be as elegant as doing a full Build->Project, but its very 
handy to be able to try to compile a single from from a project - especially 
if the recommened Build->Build Project takes a very long time (ok, it may not 
compile using the same options as if doing Build->Build Project, but its a 
quick and dirty hack to check that any chanegs done to a file kinda work).

Greetings

-- 
David Somers
VoIP: FWD 622885
PGP Key = 7E613D4E
Fingerprint = 53A0 D84B 7F90 F227 2EAB  4FD7 6278 E2A8 7E61 3D4E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://public.kitware.com/pipermail/cmake/attachments/20050721/50dcd36c/attachment.pgp