On 8/3/07, Michal Čihař <[EMAIL PROTECTED]> wrote:
> Is there
> some workaround for this so that I can produce library and executable of
> same name in one build tree?
Your CMake *target* names must be unique inside your CMakeLists.txt.
Otherwise dependency checking would fail. But the name of th
Hi
On Fri, 3 Aug 2007 10:25:59 +0200
"Eric Noulard" <[EMAIL PROTECTED]> wrote:
> Another Forget cc CMake-ML...
>
> Complement: When using other CMake macro you should use
> the primary name e.g:
>
> TARGET_LINK_LIBRARY(gammu-exe Gammu-Lib)
I found this myself meanwhile ;-).
> You should (for
Another Forget cc CMake-ML...
Complement: When using other CMake macro you should use
the primary name e.g:
TARGET_LINK_LIBRARY(gammu-exe Gammu-Lib)
-- Forwarded message --
From: Eric Noulard <[EMAIL PROTECTED]>
Date: 3 août 2007 10:23
Subject: Re: [CMake] MSVC project na
What results in having two projects in MSVC both with same name (as
project names are not case sensitive) and this obviously fails. Is there
some workaround for this so that I can produce library and executable of
same name in one build tree
Hello,
I'm not sure but you can try to make 2 d
Hi
I'm using CMake on Gammu project [1] and now when first user wants to
natively compile it using MSVC on Windows I came to problems because
both library and executable projects share same name. Currently result
of build process is libGammu library and gammu program. This is
basically done by fol
