[Cmake] CMake and KDevelop

[Roberto Raggi]

Hi!

please, take a look at the new project manager I wrote for the next major 
release of KDevelop.. KDevProject is more or less deprecated!

the source code is in the folder
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdevelop/buildtools/projectmanager/

and a simple `custom project manager' plugin (100 loc) is defined in 
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdevelop/buildtools/projectmanager/importers/custom/

the plugin for using `make' as builder is defined in
http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdevelop/buildtools/projectmanager/builders/makebuilder/

if you want to use the new `custom project manager' with the `make builder' 
you have to add these lines to your project file (<projectname>.kdevelop)

    <projectmanagement>KDevProjectManager</projectmanagement>
    <importer>KDevCustomImporter</importer>
    <builder>KDevMakeBuilder</builder>

ciao robe

On Thursday 02 September 2004 16:52, Simon Drouin wrote:
> This message comes from the CMake mailing list and has been also posted
> to kdevelop-devel because it concers kdevelop too.
>
> Alexander Neundorf wrote:
> >>Hi all,
> >>
> >>Is anyone working on a way to integrate cmake into kdevelop (apart from
> >>creating custom makefile projects into kdevelop from makefiles generated
> >>by cmake)?
> >>
> >>Thanks in advance.
> >>
> >>Simon
> >
> >I started playing with libCMakeLib.a which is built when building cmake. I
> >got so
> >far that I was able to parse all the cmakelists.txt and list the targets,
> >sources
> >and stuff.
> >If you are interested I can send you what I have so far.
> >I also downloaded the kdevelop sources but didn't get further yet.
> >I am not sure what I want to do: importing a cmake-based project, or
> >creating
> >cmake-based projects with kdevelop. I think these both cases differ.
> >I'm afraid that when creating cmake-based projects with kdevelop there
> > will be
> >problems with hand-editing the cmakelists.txt when they are created by
> >kdevelop...
> >Actually I think the ideal would be more or less to replace the
> >kdevelop-project
> >files by the cmakelists.txt.
> >
> >Bye
> >Alex
>
> I think importing a cmake-based project is a much better option than
> creating one with kdevelop. Although eventually, it would be a good idea to
> be able to create basic projects with kdevelop. But I think this could be
> separated in 2 plugins in kdevelop. A CMake build manager that can import
> and manage existing projects and a CMake project wizard that would generate
> basic CMake projects.
>
> The CMake manager would allow you to create multiple configurations.
> Editing a configuration would bring up a window similar to the cmake gui
> under windows. The manager could watch for modifications to the
> CMakeLists.txt file and reparse it to ajust source file lists in kdevelop.
> When building or running or debugging a particular configuration, the
> manager would simply set the working directory correctly.
>
> I don't know if I'll have the time to work on that anytime soon, but you
> can send me your code anyways. I'll give it a try.
>
> Simon
>
>
>
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel