Hello,
I would like to create a custom install target: install-update
The things done by this target are:
- change CMAKE_INSTALL_PREFIX to a specific directory:
CMAKE_BINARY_PREFIX/PROJECT_NAME-REVISION_NUMBER
- run "make install"
I don't know how to launch a defined target from within cmake. Is
On 10/06/2011 07:04 AM, Michael Wild wrote:
> On Thu 06 Oct 2011 05:17:00 AM CEST, Michael Hertling wrote:
>> On 10/05/2011 10:47 PM, Robert Dailey wrote:
>>> In my particular CMake project, I have three CPP files:
>>>
>>> a.cpp
>>> b.cpp
>>> c.cpp
>>>
>>> I want 'a.cpp' to be compiled
On Thu 06 Oct 2011 05:17:00 AM CEST, Michael Hertling wrote:
> On 10/05/2011 10:47 PM, Robert Dailey wrote:
>> In my particular CMake project, I have three CPP files:
>>
>> a.cpp
>> b.cpp
>> c.cpp
>>
>> I want 'a.cpp' to be compiled in all configurations (release & debug).
>> I only wan
On Wed 05 Oct 2011 05:48:12 PM CEST, Thomas Wolf wrote:
>>
>> CMake only caches this kind of information in the CMakeCache.txt file
>> in the build tree. You might want to take a look at the -C option of
>> CMake. Alternatively, you can also try to play around with the
>> CMAKE_SYSTEM_PREFIX and CM
On 10/02/2011 06:41 PM, gaurav chetal wrote:
> Frndzz..
>
> I am attaching an archive file herewith!!!..In it the ".h" file of project A
> is not able to link to the ".h" file of project B when linking the library
> of A as well as B with the executable..This is just an outline of what i
> want to
It's because VS2010 uses msbuild to build C++ projects. You can modify
verbosity level in settings menu: Tools > Options > Projects and Solutions >
Build and Run > MSBuild project build output verbosity
On Wed, Oct 5, 2011 at 10:49 PM, James Bigler wrote:
> What is this extra chatty output from?
On 10/05/2011 10:47 PM, Robert Dailey wrote:
> In my particular CMake project, I have three CPP files:
>
> a.cpp
> b.cpp
> c.cpp
>
> I want 'a.cpp' to be compiled in all configurations (release & debug).
> I only want 'b.cpp' to be compiled in DEBUG configuration.
> I only want 'c.cpp
In my particular CMake project, I have three CPP files:
a.cpp
b.cpp
c.cpp
I want 'a.cpp' to be compiled in all configurations (release & debug).
I only want 'b.cpp' to be compiled in DEBUG configuration.
I only want 'c.cpp' to be compiled in RELEASE configuration.
How can I do this?
On 05.10.2011 20:38, Alexander Neundorf wrote:
On Wednesday 05 October 2011, Peter Kümmel wrote:
And here some numbers to compare it with Qt's qmake.
I've used this project: http://kst-plot.kde.org/
which supports qmake and cmake.
Running make/ninja on a fresh compiled project
with warm caches
On 05.10.2011 21:45, Bill Hoffman wrote:
I just tried this on a machine here.
"svn co svn://anonsvn.kde.org/home/kde/branches/work/kst/portto4/kst"
CMake build:
make -j8
real3m19.131s
user16m31.866s
sys 3m25.289s
Qmake build:
real2m55.761s
user15m15.585s
sys 1m58.203
I just tried this on a machine here.
"svn co svn://anonsvn.kde.org/home/kde/branches/work/kst/portto4/kst"
CMake build:
make -j8
real3m19.131s
user16m31.866s
sys 3m25.289s
Qmake build:
real2m55.761s
user15m15.585s
sys 1m58.203s
mp/../viewitem.h:92: warning: unused par
On Tue, Oct 4, 2011 at 6:37 PM, Ben Medina wrote:
> Hello all,
>
> We're using NSIS via CPack for our Windows installer. One thing we'd
> like to change is the "Start in" directory for Windows Start menu
> shortcuts. Currently, it appears to default to the installation
> directory, but that's not
On 05.10.2011 20:38, Alexander Neundorf wrote:
On Wednesday 05 October 2011, Peter Kümmel wrote:
And here some numbers to compare it with Qt's qmake.
I've used this project: http://kst-plot.kde.org/
which supports qmake and cmake.
Running make/ninja on a fresh compiled project
with warm caches
What is this extra chatty output from? I never remember seeing it in VS
2008, but I see it in VS 2010.
>-- Build started: Project: copy_scripts, Configuration: Release x64
--
1>Build started 10/5/2011 12:38:07 PM.
1>InitializeBuildStatus:
1> Creating "x64\Release\copy_scripts\copy_script
On Wednesday 05 October 2011, Peter Kümmel wrote:
> And here some numbers to compare it with Qt's qmake.
> I've used this project: http://kst-plot.kde.org/
> which supports qmake and cmake.
>
> Running make/ninja on a fresh compiled project
> with warm caches (in seconds):
>
> qmake
And here some numbers to compare it with Qt's qmake.
I've used this project: http://kst-plot.kde.org/
which supports qmake and cmake.
Running make/ninja on a fresh compiled project
with warm caches (in seconds):
qmake cmake Ninja
Makefiles makefiles
-j10.5-0.8 1.6-
On Wednesday 05 October 2011, David Cole wrote:
> On Wed, Oct 5, 2011 at 10:51 AM, David Cole wrote:
> > On Tue, Jul 12, 2011 at 4:58 PM, Alexander Neundorf
> >
> > wrote:
> >> Hi,
> >>
> >> On Saturday 04 December 2010, Johannes Zarl wrote:
> >>> Hello,
> >>>
> >>> The compatibility matrix fo
On Wednesday 05 October 2011, Clinton Stimpson wrote:
...
> Oh, do you still want this in the bug tracker? It was a simple fix.
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=240d39
Eh, no, then.
Thanks
Alex
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://ww
Am Mittwoch, 5. Oktober 2011, 18:38:35 schrieb Peter Kuemmel:
> > So I see that one of my projects has this problem.
> > I've narrowed it down to this commit:
> > http://cmake.org/gitweb?p=cmake.git;a=commit;h=a5683f8
>
> Great! This was fast.
>
> > If I remove the code that commit adds, from the
On 10/03/2011 07:39 PM, John R. Cary wrote:
> I am using the cmakedefine mechanism for a fortran include file.
>
> If the variable is not defined, rather than
>
> /* #undef HAVE_PLASMASTATE */
>
>
> I need
>
> ! #undef HAVE_PLASMASTATE
>
> Are there existing solutions?
You might postprocess
>
> So I see that one of my projects has this problem.
> I've narrowed it down to this commit:
> http://cmake.org/gitweb?p=cmake.git;a=commit;h=a5683f8
>
Great! This was fast.
> If I remove the code that commit adds, from the current HEAD, then my
> problem goes away.
>
> When checking the XML
On Oct 5, 2011, at 9:18 AM, David Cole wrote:
> On Wed, Oct 5, 2011 at 10:09 AM, Jaime Frey wrote:
>> Thanks.
>> I see the entry in the Changelog now. I guess I didn't pick the right search
>> term when I looked at it before. Might I suggest adding a note to bug 9465
>> that the custom command
Hmm. Part of the problem might be the generators most of the folks who
follow CMake closely tend to use - I'm a command line + vim linux weenie
myself, so I'm only going to be testing a subset of the generators. I
imagine others are Windows only, etc.
One idea that comes to mind might be to put
On Wednesday, October 05, 2011 09:53:53 am Alexander Neundorf wrote:
> On Wednesday 05 October 2011, Clinton Stimpson wrote:
> > On Wednesday, October 05, 2011 08:29:00 am Marcus D. Hanwell wrote:
> > > On Wed, Oct 5, 2011 at 6:53 AM, Peter Kuemmel
wrote:
> > > > When I install the .sh version ov
On Wednesday 05 October 2011, Clinton Stimpson wrote:
> On Wednesday, October 05, 2011 08:29:00 am Marcus D. Hanwell wrote:
> > On Wed, Oct 5, 2011 at 6:53 AM, Peter Kuemmel wrote:
> > > When I install the .sh version over an existing 2.8.4 release
> > > and use "CodeBlocks - Unix Makefiles" QtCre
Hi,
I'll probably get to it in the next 1-3 weeks...
Cheers,
Johannes
>>>On 10/05/2011 at 16:51, David Cole wrote:
> On Tue, Jul 12, 2011 at 4:58 PM, Alexander Neundorf
> wrote:
>> Hi,
>>
>> On Saturday 04 December 2010, Johannes Zarl wrote:
>>> Hello,
>>>
>>> The compatibility matrix for
CMake only caches this kind of information in the CMakeCache.txt file
in the build tree. You might want to take a look at the -C option of
CMake. Alternatively, you can also try to play around with the
CMAKE_SYSTEM_PREFIX and CMAKE_SYSTEM_*_PATH variables as documented the
man-page.
Michael
Hi
On 10/5/2011 11:17 AM, Clinton Stimpson wrote:
Peter, is that your problem also? Can you edit your .cbp to remove lines like
that? Or copy it to a file with a .xml extension then open it in a program
that can check the xml (e.g. firefox).
So, what can we do to get people to try the RC's?
On Wednesday, October 05, 2011 08:29:00 am Marcus D. Hanwell wrote:
> On Wed, Oct 5, 2011 at 6:53 AM, Peter Kuemmel wrote:
> > When I install the .sh version over an existing 2.8.4 release
> > and use "CodeBlocks - Unix Makefiles" QtCreator only shows the
> > CMakeLists.txt, nothing more.
> >
> >
On Wed, Oct 5, 2011 at 10:51 AM, David Cole wrote:
> On Tue, Jul 12, 2011 at 4:58 PM, Alexander Neundorf
> wrote:
>> Hi,
>>
>> On Saturday 04 December 2010, Johannes Zarl wrote:
>>> Hello,
>>>
>>> The compatibility matrix for different versions of cmake is now complete
>>> and awaits review:
>>>
On Tue, Jul 12, 2011 at 4:58 PM, Alexander Neundorf
wrote:
> Hi,
>
> On Saturday 04 December 2010, Johannes Zarl wrote:
>> Hello,
>>
>> The compatibility matrix for different versions of cmake is now complete
>> and awaits review:
>> http://www.cmake.org/Wiki/CMake_Version_Compatibility_Matrix
>>
On Wed 05 Oct 2011 04:22:27 PM CEST, Thomas Wolf wrote:
> Hi,
>
> is there a way to disable the global caching mechanism of cmake?
> I mean the caching where cmake stores where a certain
> software package can be /was found once successfully built.
>
> I have a closed standalone build (suitable fo
On Wed, Oct 5, 2011 at 6:53 AM, Peter Kuemmel wrote:
> When I install the .sh version over an existing 2.8.4 release
> and use "CodeBlocks - Unix Makefiles" QtCreator only shows the
> CMakeLists.txt, nothing more.
>
> Seems the "CodeBlocks - Unix Makefiles" generator is broken in 2.8.6.
>
> The en
Hi,
is there a way to disable the global caching mechanism of cmake?
I mean the caching where cmake stores where a certain
software package can be /was found once successfully built.
I have a closed standalone build (suitable for e.g. a buildserver and
automatic testing) and want to make sure
On Wed, Oct 5, 2011 at 10:09 AM, Jaime Frey wrote:
> On Oct 4, 2011, at 6:56 PM, Michael Hertling wrote:
>
>> On 10/04/2011 09:20 PM, Jaime Frey wrote:
>>> Hi.
>>> I'm having some trouble with the add_custom_command() function in cmake
>>> 2.8.3. I'm using it to run a POST_BUILD command on a targ
On Oct 4, 2011, at 6:56 PM, Michael Hertling wrote:
> On 10/04/2011 09:20 PM, Jaime Frey wrote:
>> Hi.
>> I'm having some trouble with the add_custom_command() function in cmake
>> 2.8.3. I'm using it to run a POST_BUILD command on a target. The docs say I
>> can use $ in the arguments to COMMAN
Hello all,
I have been struggling with this problem for 2 days and I cannot really find
a solution.
I have a c++ application that I want to cross compile under Fedora 15 to
use it with Windows.
The packages that my app depends on are already pre-compiled in :
/usr/i686-mingw32./
I am using
Hello all,
I have been struggling with this problem for 2 days and I cannot really find
a solution.
I have a c++ application that I want to cross compile under Fedora 15 to
use it with Windows.
The packages that my app depends on are already pre-compiled in :
/usr/i686-mingw32./
I am using
On 10/04/11 09:32, Alan Hourihane wrote:
> On 10/03/11 09:46, Alan wrote:
>> Hi all,
>>
>> I'm trying to build cmake 2.8.5, but the system I'm building on doesn't
>> have a dynamic libraries, so static only.
>>
>> When cmake comes to link I get this (with debug from make)
> It turns out that CM
When I install the .sh version over an existing 2.8.4 release
and use "CodeBlocks - Unix Makefiles" QtCreator only shows the
CMakeLists.txt, nothing more.
Seems the "CodeBlocks - Unix Makefiles" generator is broken in 2.8.6.
The entry http://www.gmx.net/de/go/freephone
--
Powered by www.kitware.c
thanks for your help Alexander & Michael.
Eric
Michael Hertling a écrit :
On 10/04/2011 10:42 AM, pellegrini wrote:
Hi all,
I would need your advise about the strategy to adopt when two
executables share common object files.
Sharing object files among different targets might mean
41 matches
Mail list logo
