Compiling C in KDE
James Gray
james at grayonline.id.au
Wed Jul 12 13:09:27 UTC 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Derek Broughton wrote:
> James Gray wrote:
>
>> Like I said earlier in the thread - you can edit the Kdev project file
>> and change it from using qmake to standard gmake+Makefiles. Then in the
>> build menu you see all the targets defined in your project's Makefile.
>> The magic "F8" (IIRC) will trigger a "make" run using the default
>> target. Whatever the magic button, Kdev will show you the compiler
>> output in a panel and if there's problems, clicking on the error/warning
>> in the panel takes you straight to the offending line of code in the
>> editor - very neat.
>
> I didn't quite grasp that from your post, but it still seems really weird.
> If you have to manually edit every project file to make the build menu
> work, it seems like a bug.
I agree with you totally. What I've been doing is creating a new
project, then over-writing the generated qmake-based project file with
an old one created from a previous version of kdev. This old project
file has been stripped of all project-specific data and simply has the
framework and variables needed to use an old-fashioned gmake Makefile.
It's klunky and buggy, but it works and I haven't found ANY way to do
this directly from the IDE. Grrrr.
Cheers,
- -- James
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEtPSHwBHpdJO7b9ERApl0AKCkQl+K4JwkGCMlZOxZSx/bpxoUIACfXHey
n17inhXWH/ajtBtrc5kERFA=
=qx7n
-----END PGP SIGNATURE-----
More information about the kubuntu-users
mailing list