Building a library and executable with 300 C++ files.

[Michael Hart]

The unfortunate side effect of labeling a product Kdevelop 4 is you have
long time users like me expecting the ease of use of Kdevelop 3 and not have
egg on ones face trying to demonstrate it wondering why Kdevelop 4 is such a
radical departure from the original; I can't simply add files to a
directory/project and compile that file.

Also, guys while I love how the new intellisence works, you have given the
word IDE to your product and IDE means isolation, insulation from a build
system to most people especially the marginal people using VS

I am very disappointed that you have now spell it out for me; I am going to
have to know something about the build system cmake if I am to become
proficient at Kdevelop 4. I was really hoping that would not be the case.

Thanks

On Mon, Nov 29, 2010 at 10:21 AM, Milian Wolff <mail at milianw.de> wrote:

> Michael Hart, 29.11.2010:
> > I know this to be very simple to do with Kdevelop 3.x.y and for that
> matter
> > MV visual studio
> >
> > Today is my last attempt to use Kdevelop4 and because kdevelop3 is broken
> > under all versions of openSuSE 11.x I have to totally abandon the
> Kdevelop
> > environment in favor of something else for the only great think I see
> about
> > Kdevelop 4 thus far is the intellisence of the editor.
> >
> >
> > I have about 300 C++ files in a directory and all I want to compile them
> > into a libraries and executable without resorting to some type of manual
> > convolution with the build system such as Cmake
> >
> > Kdevelop 3 and for that matter all the other IDEs I have ever used over
> > that past 10 years you simply add the file to a project or even easier a
> > directory and you are ready to build.
> >
> > Kdevelop 4 environment seems to want me to manually manipulate
> > CMakeList.txt file.
> >
> > Is there an automated way to make these CMakeLIst.txt files?
>
> Hey Micheal.
>
> No, there is no such thing. And you probably didn#t create these 300 files
> without running make, once, did you? Isn't that an existing project which
> comes with makesfiles, e.g. from autotools back then? Why do you want to
> convert it to CMake if you don't like it? You can run make with KDevelop 4.
>
> And as I told you already on my blog [1], KDevelop 4 has no support for
> autotools (yet?), and we do want to add more wizards in the future.
>
> While I'm of course sad to see any user abandon KDevelop, and see your
> reasons, I still have to say: Generators are always limited, and CMake is
> just
> another language, more or less. Learn it and love it, or stick to old tools
> that come with autotools support. Or stay tuned until we come to a point
> where
> we also have more wizards for CMake. Just don't expect that it will all be
> hidden and being done magically in the background, that simply does not
> work.
>
> Bye
>
> [1]: for those who missed that:
> http://milianw.de/blog/google-code-in-first-
> kdevelop-documentation-screencast#comment-1092<http://milianw.de/blog/google-code-in-first-%0Akdevelop-documentation-screencast#comment-1092>
>
> --
> Milian Wolff
> mail at milianw.de
> http://milianw.de
>
> --
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20101129/9e279cf1/attachment-0001.html>