perhaps include_directories(..)
That's how I do it.
You can also print the
${SERVER_SOURCE_DIR}
variable.
MESSAGE("SERVER_SOURCE_DIR is ${SERVER_SOURCE_DIR}")
Let me know if this works.
Nick Ogden wrote:
> Hi there,
>
> I have a problem with using CMake to compile a library that I'm trying to us
Nick Ogden wrote:
Hi there,
I see you found the right list ;-).
(And I will admit I was lazy and didn't read it before on kde-devel,
which is why I'm just now answering your actual question.)
I have a problem with using CMake to compile a library that I'm trying to use
in an application th
Hi there,
I have a problem with using CMake to compile a library that I'm trying to use
in an application that I'm writing.
I have the following directory structure:
src/
| CMakeLists.txt (1)
| app/
| | CMakeLists.txt (2)
| | (app source and headers)
|
I do a simple
==CMakeLists.txt ==
add_subdirectory(foo)
add_subdirectory(bar)
add_subdirectory(baz)
==end==
If those projects don't like that, I fix them.
Clint
Bill O'Hara wrote:
Can anyone comment on the most common way to aggregate together
multiple projects built using cmake into some lar
Can anyone comment on the most common way to aggregate together multiple
projects built using cmake into some larger structure?
Lets say I have 3 tools, foo, bar and baz.
foo is standalone and has a toplevel CMakeLists.txt with a PROJECT(FOO)
bar is standalone and has a toplevel CMakeLists.txt w
From: "LaViolette, Alan"
>
> thanks that works. It is kind of a hack would be nice if the
generator
> had an option to not append the configuration.
>> It sounds like you need the PREFIX hack. Not sure if it will make
the
>> "Win32_Debug" folder for you though, you'll have to try it and see.
>>
Correct. If you just created your repository today, then it cannot
snap back to a timestamp from yesterday and get a full build tree
based on it. You must have a valid source tree in your repository as
of the most recent nightly start time (in the past) before you can do
a successful Nightly dashbo
Hi David,
Yes, that helps somewhat, thank you! I get it to now use svn and I'm ignore
the kitware.com trigger mentions as you advise that its not actually doing
the upload.
Continuous and Experimental cdash submissions seem to go through; I'm
assuming my nightly one is breaking, where it seems to
I am now setting up the NMake generator. I have everything working
correctly except for an issue with the manifests.
I have my build environment setup to build out of source and all
intermediate file go to the CMake directory. This works for all files
but the manifest, I get a *.embed.manife
thanks that works. It is kind of a hack would be nice if the generator
had an option to not append the configuration.
From: philiplow...@gmail.com [mailto:philiplow...@gmail.com] On Behalf
Of Philip Lowman
Sent: Monday, February 02, 2009 9:36 PM
To: LaViolette
rexx.exe cc.rex dasm.exe -Iblah -o something.o something.asm
When developing the support in cc.rex for dcc and dcxx, if this step failed, it
showed the errors from cc.rex. And the CMAKE error was different. So I'm
assuming that it's not even getting to that call. I could be wrong...
-Origina
On Tuesday 03 February 2009, Phil Smith wrote:
> Yes, I do mean for rexx.exe to be invoked. For the C and C++ compilers, I'm
> running cc.rex as a front-end; I was planning on doing the same for the
> assembler. I'll need to change dcxx.exe to dasm.exe at some point, but for
> now I was just trying
Yes, I do mean for rexx.exe to be invoked. For the C and C++ compilers, I'm
running cc.rex as a front-end; I was planning on doing the same for the
assembler. I'll need to change dcxx.exe to dasm.exe at some point, but for now
I was just trying to get it to fail in a "reasonable" way.
-Orig
On Friday 30 January 2009, Adolfo Rodríguez wrote:
...
> I have a project with similar requirements as Tyler's, and we effectively
> use the CMAKE_PREFIX_PATH variable. The thing is that if you ONLY want the
> FindXXX.cmake to look in the paths pointed by CMAKE_PREFIX_PATH, and not
> the standard
On Monday 02 February 2009, Phil Smith wrote:
> -- The C compiler identification is unknown
> -- Loaded CMakeASM_DIGNUSInformation - ASM_DIGNUS support is still
> experimental, please report issues CMake Error: Error required internal
> CMake variable not set, cmake may be not be built correctly. M
On Thursday 29 January 2009, Phil Smith wrote:
> zosport.cmake (in my build directory):
>
> # This is a CMake Toolchain file, required for cross-compiling using
> # the Dignus cross-compilers on Windows, compiling for z/OS.
>
> # Tell CMAKE the target system name
> SET(CMAK
les/foo.dir/foo.c.o
> Linking C executable foo
> [100%] Built target foo
> Running tests...
> Start processing tests
> Test project /tmp/build
> 1/ 2 Testing foo Passed
> 2/ 2 Testing bar ***Failed
>
> 50% te
On Tuesday 03 February 2009, Hendrik Sattler wrote:
> Dmitry Bely schrieb:
> >> If you use a toolchain file because you are cross-compiling, then you do
> >> not have this problem.
> >
> > I would like to use the same CMakeLists.txt for native Win32 and
> > cross-compiled Linux build. How to select
***Failed
50% tests passed, 1 tests failed out of 2
The following tests FAILED:
2 - bar (Failed)
Errors while running CTest
make: *** [test] Error 8
# QUESTION
#
# Is this Error 8 from make the expected result after some tests have
failed?
#
#
# Now try the Nightly test target.
#
bil
I just spent some time struggling with this macro so I wanted to post an
example. Maybe this can be used to expand on the documentation.
First you need to collect all the headers on which you want to run moc:
set (FOO_MOC_HEADERS foo_header.h)
Next, you pass these headers to the qt4_wrap_cpp mac
Nicolas Desprès wrote:
On Tue, Feb 3, 2009 at 4:23 PM, Clinton Stimpson wrote:
I'm curious what do you need it for?
I'm using a git and I have several project sharing the same submodule
as a shared library. All these projects use Qt and a set of others
libraries. I factor all the CMak
My apologies for responding earlier with an incorrect Subject line. I
hope the following will be helpful.
From: ankit jain
> The objective here to include all the .desc files in the cmakelist and
> when we make it it should generate the executable for it like if we
> include abc.desc then after
On Tue, Feb 3, 2009 at 4:23 PM, Clinton Stimpson wrote:
>
> I'm curious what do you need it for?
I'm using a git and I have several project sharing the same submodule
as a shared library. All these projects use Qt and a set of others
libraries. I factor all the CMake code searching for them in th
2009/2/3 David Cole :
> That's a great idea for a feature request. It's probably not feasible with
> out-of-the-box CVS, but you could certainly come up with an implementation
> of it for svn or any revision control system with atomic commits of multiple
> file changes at once.
I was writing somet
I'm curious what do you need it for?
Clint
Nicolas Desprès wrote:
In other word, I would like to know if someone is against requesting
QT_INCLUDE_DIR in the cache when framework are used? If no one, I'll
add a feature request.
Cheers,
Nico
On Tue, Feb 3, 2009 at 1:12 PM, Nicolas Desprès
wr
That's a great idea for a feature request. It's probably not feasible with
out-of-the-box CVS, but you could certainly come up with an implementation
of it for svn or any revision control system with atomic commits of multiple
file changes at once.
You could probably get fancy with a script that d
Hi,
Is there a way to tell ctest to only update to the next revision? I use
cmake+cdash for our build system and I would really like to get a build for
every commit if possible.
Thank you,
NS
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mai
In other word, I would like to know if someone is against requesting
QT_INCLUDE_DIR in the cache when framework are used? If no one, I'll
add a feature request.
Cheers,
Nico
On Tue, Feb 3, 2009 at 1:12 PM, Nicolas Desprès
wrote:
> Hi,
>
> I'm using cmake 2.6.2 on macosx and I'm wondering what i
Dmitry Bely schrieb:
>> If you use a toolchain file because you are cross-compiling, then you do
>> not have this problem.
>
> I would like to use the same CMakeLists.txt for native Win32 and
> cross-compiled Linux build. How to select the desired assembler then?
Just like you select the C compil
On Tue, Feb 3, 2009 at 4:43 PM, Hendrik Sattler wrote:
> Dmitry Bely schrieb:
>> On Tue, Feb 3, 2009 at 1:09 AM, Alexander Neundorf
>> wrote:
>>> On Saturday 31 January 2009, Dmitry Bely wrote:
I am trying to use JWASM (http://www.japheth.de/JWasm.html) with CMake
2.6.2 to do rather unu
David Cole wrote:
Is kde_config_version empty? Maybe it needs double quotes around it if
it is... (Or maybe it shouldn't be empty...?)
Indeed, it appears that kde_config_version is empty, and this in its
turn is because kde-config is broken.
So I guess KDE got messed up during the update, I'll
Dmitry Bely schrieb:
> On Tue, Feb 3, 2009 at 1:09 AM, Alexander Neundorf
> wrote:
>> On Saturday 31 January 2009, Dmitry Bely wrote:
>>> I am trying to use JWASM (http://www.japheth.de/JWasm.html) with CMake
>>> 2.6.2 to do rather unusual thing: cross-compile a C++ project with
>>> MASM-syntax .a
David Cole wrote:
Is kde_config_version empty? Maybe it needs double quotes around it if
it is... (Or maybe it shouldn't be empty...?)
What do you get when you run kde-config --version?
Also what is the value of KDECONFIG_EXECUTABLE in your cmake cache?
-Bill
___
Is kde_config_version empty? Maybe it needs double quotes around it if it
is... (Or maybe it shouldn't be empty...?)
On Tue, Feb 3, 2009 at 8:05 AM, Alexander Thomas <
alexander.tho...@esat.kuleuven.be> wrote:
> Bill Hoffman wrote:
>
>> Alexander Thomas wrote:
>>
>>> I have a project which uses
Bill Hoffman wrote:
Alexander Thomas wrote:
I have a project which uses Qt3, with a CMakeLists.txt containing
these lines:
find_package(Qt3 REQUIRED) # find and setup Qt3 for this project
find_package(KDE3 REQUIRED) # for kde3_automoc
add_definitions(${QT_DEFINITIONS} ${KDE3_DEFINITIONS})
Thi
Alexander Thomas wrote:
I have a project which uses Qt3, with a CMakeLists.txt containing these
lines:
find_package(Qt3 REQUIRED) # find and setup Qt3 for this project
find_package(KDE3 REQUIRED) # for kde3_automoc
add_definitions(${QT_DEFINITIONS} ${KDE3_DEFINITIONS})
This has worked fine for
Bram de Greve wrote:
Hello,
Can anyone answer this question?
I've tried the --test-timeout switch on ctest, but it seems to have no
effect.
Thanks,
Bram
Hi,
Is it possible to specify the total amount of time CTest may spend on
running the tests? With CTEST_TIMEOUT, you can set the time CTe
On Tue, Feb 3, 2009 at 1:09 AM, Alexander Neundorf
wrote:
> On Saturday 31 January 2009, Dmitry Bely wrote:
>> I am trying to use JWASM (http://www.japheth.de/JWasm.html) with CMake
>> 2.6.2 to do rather unusual thing: cross-compile a C++ project with
>> MASM-syntax .asm files for Linux under Wind
Bram de Greve wrote:
Hello,
Does anyone know how I can fix this? I need a continuous build on a
branch, but it keeps updating to the main branch
This script does that:
http://www.cdash.org/CDash/viewNotes.php?buildid=263229
Key parts are here:
if(NOT EXISTS "${CTEST_DASHBOARD_ROOT}/${CTEST
I have a project which uses Qt3, with a CMakeLists.txt containing these
lines:
find_package(Qt3 REQUIRED) # find and setup Qt3 for this project
find_package(KDE3 REQUIRED) # for kde3_automoc
add_definitions(${QT_DEFINITIONS} ${KDE3_DEFINITIONS})
This has worked fine for years, but when I now tr
ankit jain wrote:
Actually these .desc file contain only one line as:
$exec_string = "./abc"
.desc files are descriptor files for test scripts
I still can not figure out what this is supposed to do. A makefile that
does $exec_string = "./abc", does nothing other than set
The only way I could think that you could do this without making code
modifications to ctest would be to run your whole test suite itself *as* a
single test.
You could run it like this:
ctest -R "^WholeTestSuite$"
(which would run *just* the WholeTestSuite)
And then the test for running WholeTest
Hi,
I'm using cmake 2.6.2 on macosx and I'm wondering what is the rational
behind the fact QT_INCLUDE_DIR is not stored into the cache when using
framework. Here a quote of FindQt4.cmake:
IF( QT_QTCORE_INCLUDE_DIR AND NOT QT_INCLUDE_DIR)
IF (QT_USE_FRAMEWORKS)
SET(QT_INCLUDE_DIR ${QT_
Hello,
Does anyone know how I can fix this? I need a continuous build on a
branch, but it keeps updating to the main branch
Thanks,
Bram
> Hi,
>
> How can I set up a continuous build on a branch?
>
> I've tried setting CTEST_UPDATE_OPTIONS to include the branch name, but
> it keeps removing the
Hello,
Can anyone answer this question?
I've tried the --test-timeout switch on ctest, but it seems to have no
effect.
Thanks,
Bram
> Hi,
>
> Is it possible to specify the total amount of time CTest may spend on
> running the tests? With CTEST_TIMEOUT, you can set the time CTest may
> spend on
Nima Talebi schrieb:
> -DONLY=HOTWIRE_INDEP;HOTWIRE_DOC;FUNCWIRE_OVERLORD;FUNCWIRE_MINION -DDIST=1
> ..
> CMake Error: The source directory "/usr/src/hotwire-0.2.3/BUILD" does not
> appear to contain CMakeLists.txt.
> Specify --help for usage, or press the help button on the CMake GUI.
> /bin/sh: H
46 matches
Mail list logo
