On Wed, Jun 15, 2011 at 12:06 PM, Todd Gamblin wrote:
Hi Todd,
I'm the FindBoost maintainer.
I was somewhat perplexed that FindBoost doesn't properly search the default
> install layout of the boost-cmake build. i.e. if you set BOOST_ROOT to
> point to something that looks like this:
>
> thin
On 06/15/2011 09:52 PM, Dominik Szczerba wrote:
>> The FILES_MATCHING option of INSTALL(DIRECTORY ...) applies to files
>> only, i.e. with the above-noted line and BOOST_RUNTIME_DIR==/usr/lib,
>> you'll get the *whole* directory structure under /usr/lib including
>> symlinks to directories, but onl
Recently I decided to start moving some of our projects hard coded
paths into Find***.cmake modules.
Incidentally the libs are libsamplerate, libFFTW3, libsndfile,
libjemalloc, OpenEXR, OpenJPEG, libpcre.
I started out with OpenEXR, and tried to comply with the module
readme.txt, and used FindTIF
Hi Neundorf;
Thanks for your continuous help, you have helped me to solve 2 threads now.
After remove line SET (CMAKE_SYSTEM_NAME Generic) now it works.
The target device OS is Brew MP, something like eCos, but it is much simpler,
powered by Qualcomm.
At 2011-06-16 01:14:11，"Alexander Neun
I've not had a problem with this before, but I'm having an odd issue where
cmake is finding libpng when it doesn't exist on an OSX machine.
I'm using Findlibpng.cmake:
include(LibFindMacros)
find_path(LIBPNG_INCLUDE_DIR NAMES png.h PATHS
${LIBPNG_PKGCONF_INCLUDE_DIRS})
find_library(LIBPNG
http://public.kitware.com/Bug/view.php?id=11866
patch adds a file to compile with watcom to set VERSION=, adds to
wcl-386 a check for compiler version, and extends
InstallRequiredSystemLibraries.cmake to copy watcom libraries as
appropriate.
http://public.kitware.com/Bug/view.php?id=12245
(I don't
Hi All,
After having searched the cmake web site and wiki, I have been unable
to find a documented procedure for submitting patches to CMake. Via
brwosing the bug tracker and watching this list, it seems generally
apparent that a non-committer who wants to make a contribution simply
opens an iss
On 06/15/2011 11:43 PM, Dominik Szczerba wrote:
>> This behavior is really strange and I tested it in the last 10 minutes.
>> CMake says:
>> boost libs: /usr/lib/libboost_system-mt.so
>>
>> Compiling and linking with verbose reveals the link command:
>> /usr/bin/c++ CMakeFiles/test.dir/test.cp
> This behavior is really strange and I tested it in the last 10 minutes.
> CMake says:
> boost libs: /usr/lib/libboost_system-mt.so
>
> Compiling and linking with verbose reveals the link command:
> /usr/bin/c++ CMakeFiles/test.dir/test.cpp.o -o test -rdynamic
> -lboost_system-mt
>
> But a l
Am 15.06.2011 22:28, schrieb Andreas Naumann:
Am 15.06.2011 22:16, schrieb Dominik Szczerba:
I use Debian SID 64bit which is similar to Ubuntu, but not the same :)
The "problem" (if it really is one) is that debian does ship the
libraries
with another naming, so FindBoost will select the librar
Hello,
I have one small patch available here :
https://github.com/julienmalik/CMake/tree/FixFindSWIG
I read through http://www.cmake.org/Wiki/CMake/Git and
http://public.kitware.com/Wiki/Git/Workflow/Topic but could not find
the instructions for "I'm no CMake dev but have a small patch to
Am 15.06.2011 22:16, schrieb Dominik Szczerba:
I use Debian SID 64bit which is similar to Ubuntu, but not the same :)
The "problem" (if it really is one) is that debian does ship the libraries
with another naming, so FindBoost will select the library without version
number.
That's very int
> I use Debian SID 64bit which is similar to Ubuntu, but not the same :)
> The "problem" (if it really is one) is that debian does ship the libraries
> with another naming, so FindBoost will select the library without version
> number.
That's very interesting. My Boost_LIBRARIES according to cmake
Am 15.06.2011 15:12, schrieb Dominik Szczerba:
On my system, FindBoost detects the *.so without the version numbers. So, I
can update to a new (hopefully binary compatible) version without relinking.
That would be ideal, unfortunately for me (Ubuntu 10.10 64 bit cmake
2.8.4) my stuff gets
The proposed patch should be produced with:
git format-patch -1
(or -2, or -3, etc. if there is more than one commit...)
On Wed, Jun 15, 2011 at 3:52 PM, David Cole wrote:
> Please open a bug report here:
> http://public.kitware.com/Bug
>
> And attach the proposed patch as an attachment to
Please open a bug report here:
http://public.kitware.com/Bug
And attach the proposed patch as an attachment to the bug tracker entry...
Thanks,
David
On Wed, Jun 15, 2011 at 3:50 PM, MALIK Julien wrote:
> Hello,
>
> I have one small patch available here :
> https://github.com/julienmalik/CMa
> The FILES_MATCHING option of INSTALL(DIRECTORY ...) applies to files
> only, i.e. with the above-noted line and BOOST_RUNTIME_DIR==/usr/lib,
> you'll get the *whole* directory structure under /usr/lib including
> symlinks to directories, but only files and symlinks to files which
> match PATTERN/
On 6/15/2011 2:59 PM, Clinton Stimpson wrote:
For windows, only dumpbin is currently supported.
Nice thing is this is a module. So, it is easy for a project to provide
a different version. If you have a version working with objdump, we
would welcome the patch.
-Bill
Clint
On Wednesday,
On 06/15/2011 01:58 PM, Dominik Szczerba wrote:
> I am trying to copy all libboost* stuff from /usr/lib to
> CMAKE_INSTALL_PREFIX just as most users would guess:
>
> INSTALL(DIRECTORY ${BOOST_RUNTIME_DIR}/ DESTINATION
> ${CMAKE_INSTALL_PREFIX}/bin FILES_MATCHING ...)
>
> Whatever I specify fo
For windows, only dumpbin is currently supported.
Clint
On Wednesday, June 15, 2011 12:51:05 pm NoRulez wrote:
> Is objdump for MinGW compiler (BundleUtilities) in the release version of
> CMake 2.8.5 also included or is only dumpbin supported?
>
> Thanks in advance
>
> Best Regards
>
> Am 15
Is objdump for MinGW compiler (BundleUtilities) in the release version of CMake
2.8.5 also included or is only dumpbin supported?
Thanks in advance
Best Regards
Am 15.06.2011 um 20:15 schrieb David Cole :
> The CMake 2.8.5 release candidate stream continues! You can find the
> source and binar
The CMake 2.8.5 release candidate stream continues! You can find the
source and binaries here: http://www.cmake.org/files/v2.8/?C=M;O=D
Since we switched to git, and a new workflow, we're expecting to do
more frequent releases. Because of that, our release candidate phases
will be shorter than the
On Wednesday 15 June 2011, jianhua wrote:
> Hi All;
>
> No matter Linux or Windows, when try to build SHARED library, it will
> always get the following error message. ADD_LIBRARY(hello SHARED hello.c)
>
> ADD_LIBRARY for library hello is used with the SHARED option, but the
> target platform su
Hi all,
I was somewhat perplexed that FindBoost doesn't properly search the default
install layout of the boost-cmake build. i.e. if you set BOOST_ROOT to point
to something that looks like this:
boost-cmake/
include/
boost-1.41.0/
Dave,
I usually run 'ctest -j4' because it is easier to type than 'make test
ARGS=j4'.
I think that 'make test ARGS=j4' will simply call ctest with '-j4' so the
commands should be equivalent.
-kt
> -Original Message-
> From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
On Wed, Jun 15, 2011 at 3:31 AM, Andrea Galeazzi wrote:
> I think it would be great if http://public.kitware.com/Bug/view.php?id=11258
> could be fixed in 2.8.5. Without such a fix VS2010 will keep on being
> useless.
>
Hmm. I have been using VS2010 for a few weeks (not primarily I use
more than
> On my system, FindBoost detects the *.so without the version numbers. So, I
> can update to a new (hopefully binary compatible) version without relinking.
That would be ideal, unfortunately for me (Ubuntu 10.10 64 bit cmake
2.8.4) my stuff gets linked to the full name, not the symbolic link.
If
Am 15.06.2011 14:58, schrieb Dominik Szczerba:
okay, than you could use
find_package(Boost YOUR_VERSION EXACT)
Problem is boost has very complicated linking scenario. Using
FindBoost and linking to it hardcodes the versions, because they are
in the filenames! If I need to run on another sy
What cmake output do you see if you click on the green "0" numbers in the
configure column on your dahboard? It should be the full configure output.
Is your dashboard public? Can you send us a link to it?
On Wed, Jun 15, 2011 at 8:50 AM, Yngve Inntjore Levinsen <
yngve.levin...@gmail.com> wrote:
On Jun 15, 2011, at 07:55 , Dave Ohlsson wrote:
> Hi,
>
> I am new to CMake.
>
> I have a project with a few tests. The tests are independent from each
> other (run in separate directories, etc.).
>
> In my project's CMakeLists.txt, I have:
>
>enable_testing()
>add_test(NAME test1 COMM
> okay, than you could use
> find_package(Boost YOUR_VERSION EXACT)
Problem is boost has very complicated linking scenario. Using
FindBoost and linking to it hardcodes the versions, because they are
in the filenames! If I need to run on another system I must have
exactly the same boost version, bu
Hi David,
Thanks for your quick reply. I understand that it makes sense for the make
Experimental to skip the update step. Do you then mean to run something like
ctest -D ExperimentalStart\
-D ExperimentalUpdate \
-D ExperimentalBuild\
-D ExperimentalConfigure\
-
Am 15.06.2011 14:24, schrieb Dominik Szczerba:
On Wed, Jun 15, 2011 at 2:22 PM, Andreas Naumann
wrote:
Am 15.06.2011 13:58, schrieb Dominik Szczerba:
I am trying to copy all libboost* stuff from /usr/lib to
CMAKE_INSTALL_PREFIX just as most users would guess:
Why do you w
On Wed, Jun 15, 2011 at 2:22 PM, Andreas Naumann
wrote:
> Am 15.06.2011 13:58, schrieb Dominik Szczerba:
>>
>> I am trying to copy all libboost* stuff from /usr/lib to
>> CMAKE_INSTALL_PREFIX just as most users would guess:
>>
>>
>
> Why do you want to copy the boost libraries from /usr/lib to
> C
Am 15.06.2011 13:58, schrieb Dominik Szczerba:
I am trying to copy all libboost* stuff from /usr/lib to
CMAKE_INSTALL_PREFIX just as most users would guess:
Why do you want to copy the boost libraries from /usr/lib to
CMAKE_INSTALL_PREFIX? And why all of them??
I don't see any reason for t
Just found the answer:
make test ARGS=-j4
Sorry for the spam...
-- dave
On Wed, Jun 15, 2011 at 2:55 PM, Dave Ohlsson wrote:
> Hi,
>
> I am new to CMake.
>
> I have a project with a few tests. The tests are independent from each
> other (run in separate directories, etc.).
>
> In my projec
I am trying to copy all libboost* stuff from /usr/lib to
CMAKE_INSTALL_PREFIX just as most users would guess:
INSTALL(DIRECTORY ${BOOST_RUNTIME_DIR}/ DESTINATION
${CMAKE_INSTALL_PREFIX}/bin FILES_MATCHING ...)
Whatever I specify for matching I always get half of my system copied
instead of th
Hi,
I am new to CMake.
I have a project with a few tests. The tests are independent from each
other (run in separate directories, etc.).
In my project's CMakeLists.txt, I have:
enable_testing()
add_test(NAME test1 COMMAND )
add_test(NAME test2 COMMAND )
add_test(NAME test3 COMMA
"make Experimental" intentionally skips the update step. If you want to do
the same thing as "make Experimental" but add the update step, you'll have
to run ctest with appropriate -D or -M and -T arguments, or write a ctest -S
script to do the steps you'd like to do.
HTH,
David
On Wed, Jun 15,
A full clean, re-building all components whose paths have changed should
work.
Is that what you're trying to avoid?
On Wed, Jun 15, 2011 at 2:32 AM, Franz Engel
wrote:
> Hello,
>
> I have a little problem. I have to change the directory of my
> kdevelop-cmake project. But how can I do this? In
Dear developers,
I am sure this has been answered before, but I cannot find the information. I
apologize in advance for my ignorance.
I have set up our project with cmake/ctest, and have a cdash server running. I
have configured everything so that if I run in the source directory
mkdir build
On 06/15/2011 12:56 AM, Lori Pritchett-Sheats wrote:
> My project needs to create and install a Makefile that other client
> projects could import to link against our project. T
>
> I have a simple template file that generates an exported Makefile using
> the configure_file command, however I'm
Michael Hertling writes:
> Alternatively, you might use the RULE_LAUNCH_COMPILE properties to
> introduce a wrapper script for the compilations. In this way, you do
> not have to remember to configure the project with the wrapper script
> as compiler, and the script can't make any trouble during
I think it would be great if
http://public.kitware.com/Bug/view.php?id=11258 could be fixed in 2.8.5.
Without such a fix VS2010 will keep on being useless.
Il 14/06/2011 17.21, Tyler ha scritto:
I believe you're way too late for 2.8.5, but there should be a call
for bugs for 2.8.6 coming along
44 matches
Mail list logo
