From kdevelop  Wed Mar 14 09:39:30 2001
From: Alan Hilton <alanh () lineoisg ! com>
Date: Wed, 14 Mar 2001 09:39:30 +0000
To: kdevelop
Subject: Re: how to turn off -fno-exceptions in kdevelop
X-MARC-Message: https://marc.info/?l=kdevelop&m=98456287604233

Hi everyone

Have been following this discussion with some interest as it is relevant
to something I'm attempting to do.
I'm a real newbie to kdevelop and automake/autoconf but am experimenting
with the generation of Linux kernel modules.

The only way I have been able to achieve this so far is by placing
default %.o:%.c rules etc.in Makefile.am as shown below.

I have two initial questions:-
1) This approach is presumably incorrect as it bypasses
automake/autoconf?
2) Is there a better or alternative method of getting the CXFLAGS KFLAGS
etc.into the project which gives a more rounded solution?

####### kdevelop will overwrite this part!!! (begin)##########
noinst_LIBRARIES = libtest.a

libtest_a_SOURCES = timers_test.c task_manage_test.c
task_extension_test.c task_control_test.c sema4_test.c run_tests.c
msg_q_test.c 


EXTRA_DIST = msg_q_test.c run_tests.c sema4_test.c task_control_test.c
task_extension_test.c task_manage_test.c timers_test.c 

####### kdevelop will overwrite this part!!! (end)############
bin_PROGRAMS=run_tests
INCLUDES = -I/usr/src/linux/include -I/usr/src/rtai/include -I..
KFLAGS = -D__KERNEL__ -DMODULE
CFLAGS = $(INCLUDES) -Wall -Wno-unused -O2 -g -MD -fno-strength-reduce

# Uncomment this line to enable debug comments.
CFLAGS += -DZDEBUG

run_tests: run_tests.c
	$(CC) $(CFLAGS) -o $@ $<
	
# Default rules
%.o:%.c
	$(CC) $(CFLAGS) $(KFLAGS) -c -o $@ $<
	

Any advise gratefully received.

Alan Hilton

Roland Krause wrote:
> 
> Juergen raises a very important point.
> 
> KDevelop1-4 currently must try to comply with the KDE automake/autoconf
> scheme as close as possible. The concept of "per file" compiler flags
> or "per directory" compiler, linker, makefile flags does not exist
> since the concept of a file is unknown.
> 
> VC6 otoh, does not use makefiles until when they get exported. This is
> what KDevelop should do in the long run. Note that it is impossible as
> of now. KDevelop should be able to generate KDE compliant Makefile.am
> and configure.in.in's from a project not the other way around.
> Otherwise we need to maintain a minimum of 4 syntax parsers for make,
> m4, sh and perl.
> 
> VC6 is crap in almost all other respects. This they got right. An IDE
> needs to take care of the project management which includes the
> dependencies.
> 
> Roland
> 
> =====
> --
> Roland Krause
> In the garage of life there are mechanics and
> there are drivers. Mechanics wanted!
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - Buy the things you want at great prices.
> http://auctions.yahoo.com/
> 
> -
> to unsubscribe from this list send an email to kdevelop-request@kdevelop.org with the following body:
> unsubscribe »your-email-address«

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