very strange behaviour

[wysota]

Try cleaning your build and rebuilding the application from scratch (make distclean && qmake && make).

[regix]

I have made a new project with kdevelop on a fresh suse 10.0 installation. I imported only the sourcefiles, headers and ui files. I added the config macros and the libs and includes in the pro file, I ran qmake and it issued warnings about possible symbol conflicts in a lot of sourcefiles. I tried to build the project: no luck. I tried to build the subproject (what is the difference between a project and subproject??) and it compiled all the sourcefiles but failed to link the application properly

On the computer where the app is still compiling I ran make distclean in the src directory
It replied no rule to make or something like that probably because I removed all the .o files as well as the moc* files as well as the Makefile. So I ran qmake and in kdev I chose for build project and it compiled and linked fine. When I chose start debug, the application started but jumped over the breakpoint I had put in a constructor that is executed.

????
Rgx

[Big Duck]

perhaps you could try compiling with the -g and -O0, so no optimisations.
This would help when debugging, the lines dont jump around seemingly random.

And then put a watch for the variable so the debugger stops at it, or when it changes.

[regix]

no effect after compiling with O0

Rgx

[wysota]

I have made a new project with kdevelop on a fresh suse 10.0 installation. I imported only the sourcefiles, headers and ui files. I added the config macros and the libs and includes in the pro file, I ran qmake and it issued warnings about possible symbol conflicts in a lot of sourcefiles. I tried to build the project: no luck. I tried to build the subproject (what is the difference between a project and subproject??) and it compiled all the sourcefiles but failed to link the application properly

Did you clean all the temporary files (especially ones that moc created) before moving them to the new project?

[regix]

I went into the src directory and did
rm *.o
rm moc*
rm Makefile

Are there any more files I should delete?

Rgx

[wysota]

Try running 'make clean' or even 'make distclean'.

[regix]

These are the flags that are set in the makefile for compiling

CFLAGS = -pipe -O0 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Wall -W -g -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT
CXXFLAGS = -pipe -O0 -march=i586 -mtune=i686 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -g -Wall -W -g -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT

Rgx

[regix]

Hi,

The solution of the problem was found by a friend of mine who suggested that kdevelop didn't search for the executable in de src directory and that I would probably find the actual executable in this src directory. And indeed there was the executable I was expecting...
Hope this helps other people with similar problems.
Does anybody know what I should change in the .pro or Makefile so that kdevelop runs the right executable?

Rgx

[wysota]

Maybe you should change KDevelop's project settings instead?

But if you insist on changing the project file, you can set a DESTDIR variable and point it to the directory where the binary is to be stored.