Building a library and executable with 300 C++ files.
michael.george.hart at gmail.com
Mon Nov 29 15:11:18 UTC 2010
I have been spoiled by my previous IDEs and never needed to know anything
about the build environment.
I just started to get my feet wet with CMakeList.txt so what you have
written below has virtually not meaning to me.
Perhaps a little more detail would be helpful.
On Mon, Nov 29, 2010 at 10:08 AM, Leon Pollak <leonp at plris.com> wrote:
> On Monday November 29 2010, Michael Hart wrote:
> > I know this to be very simple to do with Kdevelop 3.x.y and for that
> > 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
> > environment in favor of something else for the only great think I see
> > 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?
> I use the following Cmake operator to compile everything in ./src
> file (GLOB_RECURSE MAIN_SOURCES FOLLOW_SYMLINKS ./src/*.cpp)
> Have you tried this?
> kdevelop mailing list
> kdevelop at kdevelop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop