Compiling Just One File.
michael.george.hart at gmail.com
Wed Sep 7 18:57:26 BST 2011
Either I am not making myself clear or I am not understanding how your
answers. But I am functional
To me what I want is just something nice to do. I using kdevelop 4.2.3 so I
will wait for the official release of 4.3
There is not sample to send. It is as simple as taking two files and only
wanting to compile one without building the entire project
On Wed, Sep 7, 2011 at 11:43 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> On 07.09.11 10:36:53, Michael Hart wrote:
> > >The CMake+Make support also allows to build individual object files,
> > select the .cpp in the Project tree and hit Build.
> > Yes, I would have thought that would be the logical way to compile a
> > file.
> > When I do as you recommend, the whole project get built. Which is not
> what I
> > want.
> Are you using Project->Build Selection? and the List labelled "Project
> Selection" has only your .cpp file? That works fine for me with the
> attached example cmake project. If the attached project does not work
> for you, please file a bugreport at http://bugs.kde.org. Please include
> the output from the Build toolview at the bottom, it should contain only
> the make foo.o (or make main.o) call.
> If the attached project works and your real one does not, please try
> running make yourfile.o in the build directory of your project. If that
> also rebuilds everything then your cmake files created a dependency that
> causes this. If it works on the commandline, again file a bugreport, if
> possible with a reference to your real project.
> Oh and I'm currently using KDevelop 4.3 (i.e. from git directly) not the
> last release.
> kdevelop mailing list
> kdevelop at kdevelop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop