Couple of question about new KDevelop

[Andreas Pakulat]

On 17.04.11 15:26:14, Igor Korot wrote:
> On Sun, Apr 17, 2011 at 1:27 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 16.04.11 11:04:57, Igor Korot wrote:
> >> That's not good. I think it should be quite easy to port existing
> >> tempplate from version 3 to version 4.
> >> Besides there is a plan to make wxQT in addition to wxGTK. And people
> >> are already working on it.
> >
> > KDevelop has no support for autotools, hence there's no point in
> > providing templates for autotools-based projects.
> >
> > In addition everybody is free to submit and maintain application
> > templates via bugreports or reviewboard, the develop team is too small
> > to maintain lots of different app-templates that they don't use
> > themselves. There were lots of unmaintained templates in kdev3 that
> > didn't even work.
> 
> Don't know about others, but this one worked fine without any problems.
> Now, is there a plan to support autotools-based projects in KDevelop 4?
> Maybe then this particular template can be integrated...

No, unless someone volunteers to work on the code.

> > Your best bet is running configure in the project from a shell, that'll
> > generate a Makefile which you can open as a custom-makefile project.
> 
> OK, let me go a little further:
> 
> main project directory
> |
> |
> -------> debug
> |           |----------------> Makefile
> |           |---------------> Makefile.in
> |           |---------------> src
> |
> |-----------> configure
> |-----------> src
> 
> This is what I have from the KDevelop 3 project.
> 
> So in order to open this in KDevelop 4 I should go to
> <main_project_directory>/debug and open the
> file called "Makefile". Am I right?

That won't work IIRC, you'll then not see the actual source files under
/src/. You'll have to run configure in the project directory so that the
Makefile's are in the same directory as the sources.

> > As I said, most things simply don't apply anymore. Hence there's no
> > point in asking the same questions. Anyway, if someone wants to do that
> > the team would be happy to intergate the content into the website I
> > think.
> 
> As a quick example: how do I create a .so project and link my
> application against it?

KDevelop does not have anything to do with that, its a FAQ for your
buildtool and should be answered there. 

> I understand that the answer might be different because the interface
> changed, but
> the question still remains.

Well, the only thing to be said about this particular thing is:
KDevelop does not have a GUI to add shared libraries. I don't think
thats useful in a faq, it should be put into the kdev3 vs. kdev4
comparison page.

Andreas