Hi,
I have a CMakeLists.txt file, which includes some sources (say a_src.c,
b_src.c, c_src)
and include directories as xxx, yyy in that order.
Now I need to change this include directories order to yyy,xxx only for b_src.c
and rest of sources will be using default order xxx, yyy
I appreci
On 19.04.09 18:26:48, Philip Lowman wrote:
> On Sun, Apr 19, 2009 at 6:16 PM, Sagrailo wrote:
>
> > I'm building plugins, in my CMake based projects, as shared libraries; I
> > care about Unix only, and I really, really want the installed files to be
> > named like "foo.so", and not like "libfoo.
On Sun, Apr 19, 2009 at 6:16 PM, Sagrailo wrote:
> I'm building plugins, in my CMake based projects, as shared libraries; I
> care about Unix only, and I really, really want the installed files to be
> named like "foo.so", and not like "libfoo.so". How exactly to achieve this
> with CMake (I kno
I'm building plugins, in my CMake based projects, as shared libraries; I
care about Unix only, and I really, really want the installed files to be
named like "foo.so", and not like "libfoo.so". How exactly to achieve this
with CMake (I know this issue is somewhat discussed even in FAQ, and I tried
On Sun, Apr 19, 2009 at 3:42 PM, Mike Jackson
wrote:
> I think at this point the FindBoost.cmake file is just going to have
> to have the same options that BJam has for building boost in all of
> its variations:
>
> Shared or Static libraries
> Debug or Release
> Static or Dynamic C++ Runtime Link
>> I guess multiple installations of VS is a very rare case.
>
> I pretty much doubt that, making sure a piece of software builds on
> different compilers is important for _anybody_ producing some kind of
> library thats being used by other software components.
>
> Where I work, everybody who has a
On 19.04.09 14:24:42, Piotr Dobrogost wrote:
> Andreas Pakulat wrote:
>
> > On 19.04.09 13:31:22, Piotr Dobrogost wrote:
>
> >> I get it. But wouldn't it be a GOOD THING to incorporate logic of
> >> vcvarsall.bat into cmake's module looking for VC?
>
> > That would mean it needs to find that fil
2009/4/19 Philip Lowman :
> On Sun, Apr 19, 2009 at 1:56 PM, Eric Noulard
>>
>>
>> I think the "bug" is that you may define an option which overwrite an
>> uncached var.
>
> This is exactly what I wanted to do though. In this case I don't care what
> options are being exposed to the cache, I just
I think at this point the FindBoost.cmake file is just going to have
to have the same options that BJam has for building boost in all of
its variations:
Shared or Static libraries
Debug or Release
Static or Dynamic C++ Runtime Link
Just another thing to add to the mix of possibilities.
What woul
On Sun, Apr 19, 2009 at 1:56 PM, Eric Noulard wrote:
> 2009/4/19 Philip Lowman :
> > I encountered this the other day. Is this a bug?
>
> I don't think so.
> More comment inside code:
>
> > project(Foo)
> > cmake_minimum_required(VERSION 2.6)
> > set(WTFO ON)
>
> You define the WTFO which is not
On Sat, Apr 18, 2009 at 4:23 PM, Andreas Pakulat wrote:
> On 18.04.09 11:24:48, Philip Lowman wrote:
> > On Sat, Apr 18, 2009 at 7:45 AM, Michael Jackson <
> > mike.jack...@bluequartz.net> wrote:
> > > On Apr 17, 2009, at 11:56 PM, Philip Lowman wrote:
> > > On Thu, Apr 16, 2009 at 4:27 AM, Jona
2009/4/19 Philip Lowman :
> I encountered this the other day. Is this a bug?
I don't think so.
More comment inside code:
> project(Foo)
> cmake_minimum_required(VERSION 2.6)
> set(WTFO ON)
You define the WTFO which is not cached.
> message("WTFO is ${WTFO}")
> option(WTFO "wtfo" OFF)
Now yo
Hi there,
2009/4/19 Piotr Dobrogost :
> [...]
> Would it be a good idea to make cmake be able to find VS even if these
> environment variables weren't set? Maybe using registry or just looking
> at default installation folder?
It is not only about finding visual studio but also about configuring
Am Sonntag 19 April 2009 14:24:42 schrieb Piotr Dobrogost:
> Andreas Pakulat wrote:
> > On 19.04.09 13:31:22, Piotr Dobrogost wrote:
> >> I get it. But wouldn't it be a GOOD THING to incorporate logic of
> >> vcvarsall.bat into cmake's module looking for VC?
> >
> > That would mean it needs to find
On Sunday 19 April 2009, Piotr Dobrogost wrote:
> Hi
>
> Below is a list of spelling errors in
> http://cmake.org/cmake/help/cmake2.6docs
>
> confguration
> availble
> behaviour
> lanauges
> successfull
> posibilities
> DEFINTIIONS
> incude
> standartized
> ompiler
> Esentially
> acces
> compatibil
I encountered this the other day. Is this a bug?
project(Foo)
cmake_minimum_required(VERSION 2.6)
set(WTFO ON)
message("WTFO is ${WTFO}")
option(WTFO "wtfo" OFF)
message("WTFO is ${WTFO}")
Here's the output...
(first run)
WTFO is ON
WTFO is OFF
(second run)
WTFO is ON
WTFO is ON
--
Philip
Hi
Below is a list of spelling errors in
http://cmake.org/cmake/help/cmake2.6docs
confguration
availble
behaviour
lanauges
successfull
posibilities
DEFINTIIONS
incude
standartized
ompiler
Esentially
acces
compatibilty
seach
NAMEand
acutal
onthis
defaultis
--
Piotr Dobrogost
*** curlpp.org - c+
>> I guess multiple installations of VS is a very rare case.
>> Wouldn't reading VS variables in registry help?
>>
>
> Not if you are on a yearly academic licensing program. Every developer
> in our department has at least 3 versions of Visual Studio installed.
>
> John
>
--
John M. Drescher
__
I have the following CMakeLists.txt to create installer of several DLLs
I need to ship with my application:
CMAKE_MINIMUM_REQUIRED(VERSION 2.6)
CMAKE_POLICY(VERSION 2.6)
# Variables
SET(SBILIB_TITLE sbiLib)
SET(SBILIB_VERSION 1.0)
# Project name
PROJECT(SBILIB)
# Install
INSTALL(
FI
Andreas Pakulat wrote:
> On 19.04.09 13:31:22, Piotr Dobrogost wrote:
>> I get it. But wouldn't it be a GOOD THING to incorporate logic of
>> vcvarsall.bat into cmake's module looking for VC?
> That would mean it needs to find that file as first thing, because that
> file actually uses its own a
On 19.04.09 13:31:22, Piotr Dobrogost wrote:
> Bill Hoffman wrote:
>
> > That is by design. Even if CMake did find them, the user would still
> > need to set them in order to use the command line tools. CMake makes
> > the simple assumption that the compiler is installed and running in the
> >
Bill Hoffman wrote:
> That is by design. Even if CMake did find them, the user would still
> need to set them in order to use the command line tools. CMake makes
> the simple assumption that the compiler is installed and running in the
> environment CMake is running in.
I get it. But wouldn't
Am Sonntag 19 April 2009 00:55:12 schrieb Piotr Dobrogost:
> Hi
>
> Recent thread titled "CMAKE_MAKE_PROGRAM is not set." shows cmake needs
> some environment variables to find VS command line tools.
> Setting of these variables is done by running a bat file that comes with
> VS. This seems a littl
On 19.04.09 00:55:12, Piotr Dobrogost wrote:
> Recent thread titled "CMAKE_MAKE_PROGRAM is not set." shows cmake needs
> some environment variables to find VS command line tools.
> Setting of these variables is done by running a bat file that comes with
> VS. This seems a little fragile.
Why do yo
24 matches
Mail list logo
