Bug#27346: Perhaps a better way to handle Makefile.in/configure.in and Family on basic Console Apps

Van vanboers at dedserius.com
Mon Jun 18 09:26:41 UTC 2001

KDevelop is by far the best Linux/UNIX IDE I've tried, but, it would simplify
development/troubleshooting greatly if, when you create a C application from the
wizard all the KDE/X stuff doesn't go into the macros for configure.in/am
Makefile.in/am.  They get huge, and, can take hours/days to troubleshoot when
they don't pertain to a simple console application, 

Once done with the wizard, I'd like to be able to delete main.c (hello world)
and create src and Documentation directories.  

I'd like to then add existing file thisfile.c thatfile.c thatfile.h into the src
directory and have the aclocal do it's magic along with
autoscan/autoheader/autoconf/automake and coordinate with the root .kdevprj file
without incorpating any GUI includes/defines/libs at all.  Quick development of
console, esp. esecurity apps will promote the migration to the Linux Desktop
more quickly.

MicroSoft VisualC++ allows these types of processes, but, not nearly as
seemlessly as the basic C console application in KDevelop.  You guys really have
a huge opportunity here to convert those C developers, and c development is far
from dead.

If security-minded types can use a strong OSS IDE like KDevelop to put those
applications together quickly, KDE will have a much greater opportunity in the
Desktop Market.

My 2 cents, but, we're all on the same team, I hope.

Pardon my rant, but, I've spent the weekend switching from emacs bloatware to
resolving to the tried-and-true vi, since some things never change what you :w.

Best Regards,
Linux rocks!!!   http://www.dedserius.com/

to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«

More information about the KDevelop-devel mailing list