I've followed your instructions, removed the obsolete lines but
no effect, the libbrOpenGL.dll which is located at ./lib is still
missing on startup ...
The br* stuff are my dependencies library which I've created
and installed separatelly, not in context of the actual project.
The resulting d
Am Donnerstag, den 12.05.2011, 17:10 +0200 schrieb Michael Wild:
> I agree, that this behaviour is due the fact that the parameter name
> "var" hides the parent-scope variable "var", but then ${${var}} should
> IMHO result in an error or warning message. Essentially, what this does
> inside the fun
It is under Source/QtDialog and the cmake option has QtDialog in its name.
Clint
- Reply message -
From: "Dick Munroe"
Date: Thu, May 12, 2011 11:07 am
Subject: [CMake] How do you go about building the cmake-gui from source in
2.8.4?
To:
The title pretty much says it all. I can'
Hello,
I'm currently playing with imported / exported targets.
Let's say I build a project A for both static and shared variants.
A depends on a 3rd party static library called B.
Internally, B depends on another static library called C.
My project A builds fine.
But when I try to export my targ
Hello,
I have some trouble to link my project to the imlib2 library. The
library is installed correctly and a command like :
gcc test.c -o test `pkg-config --libs --cflags imlib2`
works and link to imlib2.
I have this CMakeLists.txt http://markand.malikania.fr/CMakeLists.txt
but it does not
The title pretty much says it all. I can't find anything obvious in the
source tree and I want to rebuild cmake-gui for windows.
tia,
Dick Munroe
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/open
Hi
Background:
I've run a set of tests using:
ctest -D ExperimentalTest
(i.e. delaying the CDash submit)
These tests take a long time to complete. Now I notice one of the tests
failed because I forgot to update it after a change to my program.
I can re-run that particular test using someth
Am Donnerstag, 12. Mai 2011, 14:51:42 schrieb Heine, Christian:
> Hmm, this is strange. I've followed your instructions, but those take no
> effect. When i try to run the executable I got the failure message box that
> my libbrOpenGL.dll of the acutal build result is missing. Here is what I do
> on
I agree, that this behaviour is due the fact that the parameter name
"var" hides the parent-scope variable "var", but then ${${var}} should
IMHO result in an error or warning message. Essentially, what this does
inside the function is
set(var var)
which is hardly ever what is intended. This could
If you really wanted to pass the name of the variable in rather than the
value, then as Rolf says the behaviour you get is as expected. The only way
round that would be to rename var in the function to something guaranteed
not to be the name of a variable that you ever tried to pass in.
Or you co
Hmm, this is strange. I've followed your instructions, but those take no effect.
When i try to run the executable I got the failure message box that my
libbrOpenGL.dll
of the acutal build result is missing. Here is what I do on demo build:
INCLUDE_DIRECTORIES(${CMAKE_CURRENT_BINARY_DIR}
Am Donnerstag, den 12.05.2011, 11:50 +0100 schrieb Glenn Coombs:
> I think you probably wanted to write and call your function like this:
>
> FUNCTION(build var)
>MESSAGE(STATUS "var: ${var}")
> ENDFUNCTION(build)
>
> SET(var red blue yellow green)
> build("${var}")
>
> That prints out a
Often one wants to pass in the *name* of a variable (i.e. the name of
list, like for list(APPEND name ...)), so Rolf's code does make sense.
Haven't had the time to try the test-case myself, though...
Michael
On 05/12/2011 12:50 PM, Glenn Coombs wrote:
> I think you probably wanted to write and c
Am Donnerstag, 12. Mai 2011, 12:40:54 schrieb Heine, Christian:
> Thanks Eike for this hint! This works, but I couldn't use it.
>
> One reason is, that any module is loosely coupled. It doesn't know where the
> other modules it's depends on are located. By this reason I need a place
> where any fi
I think you probably wanted to write and call your function like this:
FUNCTION(build var)
MESSAGE(STATUS "var: ${var}")
ENDFUNCTION(build)
SET(var red blue yellow green)
build("${var}")
That prints out as you would expect:
-- var: red;blue;yellow;green
--
Glenn
On 12 May 2011 07:27,
Thanks Eike for this hint! This works, but I couldn't use it.
One reason is, that any module is loosely coupled. It doesn't know where the
other modules it's depends on are located. By this reason I need a place where
any final library is archived and could be linked by the executable at runtim
> Hi,
>
> I'm not sure that I'm on the right path, therfore I will explain what I
> will do. I'm migrating our Linux project to Windows plattforms. Our
> project is build on several modules, which have to create and installed as
> libraries with cmake, some modules have dependencies to other module
Hi,
I'm not sure that I'm on the right path, therfore I will explain what I will
do. I'm migrating our Linux project to Windows plattforms. Our project is build
on several modules, which have to create and installed as libraries with cmake,
some modules have dependencies to other modules. So fa
Am Donnerstag, den 12.05.2011, 11:15 +0300 schrieb tiantik:
> Hi CMake's members,
>
> My project has two parts: shared library and executable. The soversion
> of shared library is libxxx.so.1.2.3. Now, the cmakelist.txt of
> executable will check this soversion of shared library as . How do I
> do
Hi CMake's members,
My project has two parts: shared library and executable. The soversion of
shared library is libxxx.so.1.2.3. Now, the cmakelist.txt of executable will
check this soversion of shared library as . How do I do this checking?
Thanks.
___
20 matches
Mail list logo
