KDevelop 3.0 and cross compilation

[Daniel Junglas]

Hi there,

roughly a month ago, I have posted a message to the forum that talked
about cross compilation in KDevelop 2.x and 3.0.
It seems that traffic on this forum is very low, so I try again here.

	Hi all,
        I recently tried to use KDevelop for cross development. That
        failed completely. Now I read on the main kdevelop page that
        KDevelop is completely rewritten for version 3.0. A good time
        to ask for some features, I thought.
        o would it be possible to let the user select a debugger,
        instead of hardcoding 'gdb'? I think it would be ok, if the
        debugger to be selected must have the same interface as gdb.
        Nevertheless, at the moment I cannot even use a cross gdb
        without doing a lot of tricks, such as using symbolic links,
        changing my $PATH variable, ...
        o would it be possible to use user defined project templates?
        At the moment one can only select Qt/Midi/Terminal/...
        Application. For my cross development stuff it would have been
        very nice if I had been able to setup a project template that
        automatically selects cross tools, such as compiler, linker,
        ...
        o is it possible to make compiler, linker, ... a per-project
        option?
        o if you are still sticking to the configure scripts, could
        you please adjust the project creation wizards such that
        arguments to the initial run of configure are possible?
        Also, I think it would be better to select compiler, linker
        etc. in the project creation wizard, wouldn't it?
        All in all, it is just one big feature that I request:
        "Please make cross development in KDevelop 3.0 a lot easier"
        Thanks a lot

I think a lot of the above features may be easily achieved by the use of
environment variables, such as CC, CXX, ...
If only KDevelop would not overwrite them ...

I highly appreciate any feedback (positive and negative).

	Daniel

PS: I am not a member of the mailinglist, so it would be nice if you'd cc
    me.


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