Am Mittwoch, 6. Juni 2012, 16:15:52 schrieb Natalie Tasman:
> Andreas, thank you for your help. Not surprisingly (for someone new
> to cmake) I was getting tripped up with the cmake cache, in part.
> Here's what I've found using cmake 2.8.8:
>
> 0) One can get tripped up working with the both GUI
On Wed, Jun 6, 2012 at 8:20 PM, Mikael Lyngvig wrote:
>> On Sun, May 6, 2012 at 4:58 PM, Rahul Garg wrote:
>> Just wondering, which version of CMake does "Mastering CMake 5th
>> edition" cover?
>
> Nobody seems to have answered this yet. A picture in the book shows CMake
> v2.6. I can't find an
Nobody seems to have answered this yet. A picture in the book shows CMake
v2.6. I can't find any direct reference to the version number, though.
Cheers,
Mikael
-- Love Thy Frog!
2012/6/5 Klaim - Joël Lamotte
>
>
> On Sun, May 6, 2012 at 4:58 PM, Rahul Garg wrote:
>
>> Hi.
>>
>> Just wonderi
On Jun 6, 2012, at 7:20 PM, Natalie Tasman wrote:
[...]
> However, I would like a way to tell find_package that it must find
> both the library and header files from the same prefix. Specifically,
[...]
I solved this some time ago by not using find_package(). The following works
for Linux sy
Using cmake 2.8.8, I know that I can add "backup" or "fallback" search
directories for find_package, using
INCLUDE_DIRECTORIES(/opt/local/include)
LINK_DIRECTORIES(/opt/local/lib)
In this case, cmake first searches its default paths and THEN the
specified alternate.
However, I would like a way
Andreas, thank you for your help. Not surprisingly (for someone new
to cmake) I was getting tripped up with the cmake cache, in part.
Here's what I've found using cmake 2.8.8:
0) One can get tripped up working with the both GUI and the command
line. I was manually clearing cache files from the c
> NoRulez,
A better question is "Why was revision 8 not included in the nightly run?"
Using one source tree for both continuous and nightly assumes that there will
be no continuous runs between the last update incorporated in the nightly run
and the time at which the nightly run is performed. I
Am 06.06.2012, 08:57 Uhr, schrieb NoRulez :
Hello,
here is the build process of the build server:
1.) e.g.: last commit at 03:00 pm (svn revision 8) => build is ok
2.) The nightly build starts at 10:00 pm (svn revision 7) => build is ok
Why is the svn revision before the last commit, it sh
aha.
Thanks
The command
find_library(PCRE_LIBRARY pcre
PATHS ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
)
is working perfectly issue was that it was reading the variable value from
the cache after deleting cache it is finding library
at {CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
regards
Vivek
I am using sed to remove that message
sed -e '/is newer than depender/D'
regards
Vivek Goel
On Mon, Jun 4, 2012 at 9:53 PM, vivek goel wrote:
> How to remove warning message
> Dependee is newer than depender
> When I am not running make in verbose mode.
> I want to show this warning/info mess
Please cc the list so others may benefit from the discussion.
Then you need two find_library calls. One to find it in your custom
directory with NO_DEFAULT_PATH, and then if it's not there, the same call
again without the NO_DEFAULT_PATH.
HTH,
David
On Wed, Jun 6, 2012 at 2:25 PM, vivek goel
regards
Vivek Goel
On Wed, Jun 6, 2012 at 11:05 PM, vivek goel wrote:
> sorry for typo it was path.
>
path=paths :)
> but still it doesn't work
> find_library(PCRE_LIBRARY pcre
> HINTS ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
> PATHS ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
> )
>
> ag
sorry for typo it was path.
but still it doesn't work
find_library(PCRE_LIBRARY pcre
HINTS ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
PATHS ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
)
again output is /usr/lib/x86_64-linux-gnu/libpcre.so
regards
Vivek Goel
On Wed, Jun 6, 2012 at 10:52 PM,
Hello list,
I have the following directory layout
TopLevel
-- Dir1
-- CMakeLists.txt (3)
-- foo.cpp
-- Installation
-- CMakeLists.txt (2)
-- CMakeLists.txt (1)
with (1)
add_subdirectory(Installation)
and (2)
enable_testing()
add_subdirectory("${CMAKE_SOURCE_DIR}/Dir1" "$
Hi,
On Wed, Jun 6, 2012 at 5:40 PM, vivek goel wrote:
> I am using following command to find pcre library
>
> SET(CMAKE_LIBRARY_PATH "${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib")
> All compiled library are located in
> ${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
>
> find_library(PCRE_LIBRARY
On Fri, Jun 1, 2012 at 6:47 PM, Zaheer Chothia wrote:
> Projects generated by the wizard within Visual Studio have the version set to
> 11.0, as was the case with Intel Fortran 11.x and 12.x. This issue is easy to
> diagnose (see patch following this mail) and I have tested that it works with:
>
On Wed, Jun 6, 2012 at 10:29 AM, Bill Hoffman wrote:
> On 6/5/2012 12:09 PM, Peter Kümmel wrote:
>> On 05.06.2012 17:12, Dave Abrahams wrote:
>>> But when I install cmake the traditional way it works. It looks like
>>> CMake doesn't tolerate being installed in a path containing "=".
>>
>> CMake gu
I am using following command to find pcre library
SET(CMAKE_LIBRARY_PATH "${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib")
All compiled library are located in
${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib
find_library(PCRE_LIBRARY
pcre
PATH
${CMAKE_SOURCE_DIR}/lib/linux/gcc/${BIT}/lib}
But every-ti
On 6/4/2012 12:09 PM, Bill Hoffman wrote:
Looks like you are not linking all the libraries you are using or you
left source code out of the project. Where does this symbol come from:
for_write_seq_fmt_xmit
I have been told that you are missing the link library libifcore.
-Bill
--
Bill Hoff
On 6/5/2012 12:09 PM, Peter Kümmel wrote:
On 05.06.2012 17:12, Dave Abrahams wrote:
But when I install cmake the traditional way it works. It looks like
CMake doesn't tolerate being installed in a path containing "=".
AH! seems that's the problem.
CMake guys: is this a bug or a "feature"?
On 6/6/2012 7:14 AM, Peter Kümmel wrote:
Here the actual status of the Ninja generator.
The generator now uses Ninja's build-in response support.
- MSVC10
Dependency checking is still missing as essential feature,
but the rest is quite good:
The following tests FAILED:
82 - BuildDepends (Fa
Here the actual status of the Ninja generator.
The generator now uses Ninja's build-in response support.
- MSVC10
Dependency checking is still missing as essential feature,
but the rest is quite good:
The following tests FAILED:
82 - BuildDepends (Failed)
140 - CTestGTMCover
22 matches
Mail list logo
