Am Tuesday 04 November 2008 22:45:57 schrieb Alexander Neundorf:
So, if e.g. CMAKE_FIND_ROOT_PATH is /opt/eldk-4.1/ppc_4xxFP/ppc_4xxFP ,
then I would have to query pkg-config for the variable prefix, then
prepend this prefix with the directory (the right one) from
CMAKE_FIND_ROOT_PATH, and
Am Wednesday 05 November 2008 00:57:36 schrieb Alexander Neundorf:
On Tuesday 04 November 2008, Hendrik Sattler wrote:
Am Tuesday 04 November 2008 22:45:57 schrieb Alexander Neundorf:
So, if e.g. CMAKE_FIND_ROOT_PATH is /opt/eldk-4.1/ppc_4xxFP/ppc_4xxFP ,
then I would have to query pkg
Am Thursday 06 November 2008 22:15:21 schrieb Eric (Brad) Lemings:
Eric Noulard wrote:
2008/11/6 Michael Jackson [EMAIL PROTECTED]:
All this is asking is 2 extra commands.
You may perfectly do that with autotools too:
mkdir build
cd build
/path/to/source/configure
make
make
Jed Brown schrieb:
The FindPkgConfig.cmake module looks broken too, it assumes that
-L/A -la -L/B -lb
is equivalent to
-L/A -L/B -la -lb
I don't see where the above would fail.
This can also fail, but I should have written
-L/B -L/A -la -lb
since the existing modules are
Am Tuesday 11 November 2008 19:13:43 schrieb Fernando Cacciola:
target_link_libraries, which is GREAT, is actually pretty useless
without target_include_directories, target_add_definitions and
TARGET_CMAKE_CXX_FLAGS.
Did you notice set_property(TARGET .)? There, you can do add target
Colin D Bennett schrieb:
However, I would argue that target_link_libraries vs.
link_libraries is more important than the possible
target_include_directories vs. include_directories, since the linked
libraries will directly affect the generated output (linking to
unnecessary libraries is
Bill Hoffman schrieb:
OTOH, it could make sense to do the following:
find_packge( CGAL REQUIRED components )
include( ${CGAL_USE_FILE} )
add_executable( program ... )
use_CGAL( program )
so it works now with 2.4, and eventually upgrade it to use target
properties instead.
Fernando Cacciola schrieb:
Hendrik Sattler wrote:
Bill Hoffman schrieb:
OTOH, it could make sense to do the following:
find_packge( CGAL REQUIRED components )
include( ${CGAL_USE_FILE} )
add_executable( program ... )
use_CGAL( program )
so it works now with 2.4
Am Wednesday 12 November 2008 17:03:04 schrieb Fernando Cacciola:
Hi Hendrik,
But it is not backwards-compatible and will fail to link on the new
version while it worked fine on the old version.
Why??
Because if the ${FOO_USE_FILE} doesn't do what it always does (globally
adding
Am Friday 14 November 2008 04:18:59 schrieb Fernando Cacciola:
In preparing the cmake build system for CGAL I'm having this issue:
Users can define CGAL_DIR explicitely when configuring their own
programs in order to allow find_package(CGAL) to locate CGALConfig.cmake.
OTOH, if
shoosh moosh schrieb:
I tried typing
CC=gcc ./bootstrap
but it still didn't work.
Is gcc really installed?
Can someone tell me how to fix this error. I'm working on ubuntu.
This should also work but may not be the latest release:
apt-get install cmake
HS
shoosh moosh schrieb:
cmake_bootstrap_8199.test.c:5:18: error: stdio.h: No such file or directory
Install a complete build environment, please. On Debian this is apt-get
install build-essential which includes the libc6-dev packages that you
are missing.
You know that you can search online which
Fernando Cacciola schrieb:
Nope... my users don't want to do that... (or rather I don't know which
DESTDIR, if any, they'll use at all, so the solution cannot involve
anything like it)
They want to install CGAL in the correct place, whatever that is, but
without FindCGAL.cmake unless
Fernando Cacciola schrieb:
and install the CGALConfig.cmake, only.
It doesn't make sense to install both at the same time.
Not really... FindCGAL.cmake basically locates and loads
CGALConfig.cmake, which is better placed in the install tree since the
binary folder (where it is first created)
Am Friday 14 November 2008 15:34:10 schrieb Fernando Cacciola:
stuff, there, that you cannot do in CGALConfig.cmake?
One particular stuff that can't possibly be done in CGALConfig.cmake:
locating it (CGALConfig.cmake).
find_package() would automagically locate and load FindCGAL if it finds
Am Friday 14 November 2008 19:00:25 schrieb Alexander Neundorf:
On Friday 14 November 2008, shoosh moosh wrote:
I'm trying to install cmake. I downloaded it from the cmake.org
website. Then I changed the directory to the location of the source.
Then I typed ./bootstrap in the terminal and I
Am Saturday 22 November 2008 15:17:12 schrieb Vladimir Prus:
Michael Jackson wrote:
On Nov 22, 2008, at 8:01 AM, Vladimir Prus wrote:
Bill Hoffman wrote:
Robert Dailey wrote:
Hi,
I've done some googling on how to set warning levels for visual
studio
projects generated with CMake
Am Sunday 23 November 2008 10:35:03 schrieb Andreas Pakulat:
On 23.11.08 11:24:23, Ioan Calin Borcoman wrote:
Would it be possible to add support for libtool in a cmake module? I
understand that this would be against cmake's policy of not depending
on external apps, but it could be a
Am Monday 24 November 2008 17:36:10 schrieb Bill Hoffman:
Robert Dailey wrote:
You guys have managed to steal my thread and get completely off topic.
Can anyone answer my original question please?
ZERO_CHECK is essential to the build working. ALL_BUILD is useful as
it creates the
Am Saturday 29 November 2008 00:13:26 schrieb Klaus Drechsler:
How can I prevent cmake from adding 'myextlib' to any other targets? I
only want it to be added to 'func1' nowhere else.
Or, if this is not possible, how can I propagate the link directory and
include directory 'up' to the target
Robert Dailey schrieb:
I generally like keeping libraries in version control because it makes it
convenient to start working from a fresh checkout. This is really only an
issue with Windows, since most linux distributions have a package management
system that makes it trivial to install third
Maik Beckmann schrieb:
Am Montag, 1. Dezember 2008 schrieb Micha Renner:
Why is it helpful to know the location of the Windows-DLL during the
build-process?
mingw's linker ignores the import .lib and takes .dll directly.
AFAIK, it can use both, means unlike msvc it doesn't depend on the
[EMAIL PROTECTED] schrieb:
The reason for my choice at that time was user acceptance. I had a
brief window of opportunity to introduce a new build system based on
CMake, which did not give me time to train all the developers in CMake
before deploying it. One of the first objections I
Robert Dailey schrieb:
On Mon, Dec 1, 2008 at 9:54 AM, Hendrik Sattler [EMAIL PROTECTED]wrote:
I would keep this separate. You only need to setup the environment once.
This is a completely different task then the actual development.
Additionally: why not provide one package for your
Robert Dailey schrieb:
On Mon, Dec 1, 2008 at 10:21 AM, Hendrik Sattler [EMAIL PROTECTED]wrote:
Robert Dailey schrieb: Well on Linux this would be trivial, but as I said
on Windows doing this
could take hours, even if I do provide a simple package they can extract
to
some directory
Robert Dailey schrieb:
This makes absolutely no sense to me. To copy all relevant files, I have
to know their name. To know their name, I need to know the platform and the
build configuration, since as I said before the names are different in both
cases.
How do you link against them if you do
Am Tuesday 09 December 2008 18:09:23 schrieb kafou nmento:
Hi all!
I'm compiling a Qt based libtorrent app with CMake using MinGW generator.
For those not knowing libtorrent, it is a lib fully boost based. (boost
version used 1.34.1). 100% of the build goes well. But at the linking it
fails
Am Wednesday 10 December 2008 13:23:04 schrieb Clemens Arth:
Clemens Arth wrote:
before I submit a bug report I wanted to ask you about some strange
behaviour of TARGET_LINK_LIBRARIES on MacOS 10.5 and CMake 2.6-2;
A library is created for debug and release, named libFooD.dylib and
Am Wednesday 10 December 2008 19:50:42 schrieb David Genest:
David Cole wrote:
Line 2009 of CMake/Source/cmake.cxx chooses the default Visual Studio
generator. Looks like that block of code forgot to update itself when
Visual Studio 9 support was added.
We should, of course, prefer the
Am Thursday 11 December 2008 00:46:24 schrieb James Bigler:
I have a library which depends on libpng. If libpng is shared, then I
don't need to know that libpng links agains libz, but if libpng is static,
then I better well know that libpng needs libz so that when I need to
eventually link
Am Friday 12 December 2008 12:41:47 schrieb tormod.ravnanger.lan...@dnv.com:
The output with VS2008 is:
Did you try the NMake Makefiles generator?
HS
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Michael Wild schrieb:
if (NOT WIN32)
# use pkg-config to get the directories and then use these values
# in the FIND_PATH() and FIND_LIBRARY() calls
find_package( PkgConfig REQUIRED )
pkg_check_modules( _sigcxx2 REQUIRED sigc++-2.0 )
endif (NOT WIN32)
pkgconfig can also be used on
Am Thursday 18 December 2008 20:03:25 schrieb Philip Lowman:
Could you try the following beta FindGTK2 module?
Set CMAKE_MODULE_PATH prior to calling FIND_PACKAGE(GTK2 COMPONENTS gtk)
See the module for details
Some notes: you should make better use of path suffixes in find_file instead
of
Am Thursday 08 January 2009 00:13:55 schrieb Robin Vobruba:
Also, i usually generate GCC makefiles with CMake, and they use only
timestamps. Make itsself does not have the functionality integrated,
as much as i know, so it has to be added by cmake. Automake eg, also
adds this functionality to
Am Wednesday 07 January 2009 23:54:05 schrieb Albert Astals Cid:
Hi, i'm new to the list, so i'm not sure if this is the correct procedure,
i read a bit in the wiki and it seems it is, so here i am.
I want to add upstream the two attached modules so we don't have to
maintain them in poppler.
Philip Lowman schrieb:
On Fri, Jan 9, 2009 at 7:32 AM, Philip Lowman phi...@yhbt.com wrote:
On Thu, Jan 8, 2009 at 5:22 PM, Albert Astals Cid aa...@kde.org wrote:
if (LibOpenJPEG_OPENJPEG_LIBRARY)
set (LibOpenJPEG_LIBRARIES ${openjpeg_LIBRARY})
endif (LibOpenJPEG_OPENJPEG_LIBRARY)
If
Am Thursday 15 January 2009 18:13:43 schrieb Robert Dailey:
On Thu, Jan 15, 2009 at 10:07 AM, Michael Jackson
mike.jack...@bluequartz.net wrote:
To look for the Compiler being used..
IF (MSVC60)
SET (...)
ENDIF (MSVC60)
IF (MSVC71)
SET ()
ENDIF(MSVC71)
IF
Am Sunday 18 January 2009 12:09:21 schrieb Eric Noulard:
For supporting this CMake would have to elaborate a way to figure out
what no meaningful changes in CMakeLists.txt means :=)
Write temporary solution/project files and compare them? If I change MacOS X
stuff only, a visual studio build
Alan W. Irwin schrieb:
Can somebody recommend a fix to that file so that CMake-2.6.2 works just as
well as CMake-2.4.8 for the macada version of the gcc compiler?
I have no idea whether gcc should always be expected to recognize the
-current_version flag.
Martin Costabel schrieb:
Alan W. Irwin wrote:
[]
Is there a better gcc option then -v to find out the _actual_ linker
being
used?
Use -Wl,-v :-)
On 10.4, if you run gcc -dynamiclib, the linking is managed by
/usr/bin/libtool which in turn calls /usr/bin/ld, and /usr/bin/libtool
Anders Backman schrieb:
so set_target_properties(target PROPERTIES VERSION 1.1 SOVERSION 1.1)
doesnt work under windows then?
No. A RC file is not created automatically. A bit complicated as other
information is included in that file, too. However, you can use
configure_file to automatically
Anders Backman schrieb:
Hi all
Old issue, but Im trying to set dll version from CMAKE on dynamic libraries.
After reading docs/release info I saw that version 2.4.4 included this
functionality.
However, Im trying without any success.
So IS this supported or not?
SET_TARGET_PROPERTIES(
Philip Lowman schrieb:
Do you know if there is a way to append this information to the DLL with the
linker (FileVersion ProductVersion), instead of generating an RC file?
No.
HS
___
CMake mailing list
CMake@cmake.org
Am Samstag 31 Januar 2009 14:12:24 schrieb Dmitry Bely:
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 Windows. JWASM itself emulates
MASM excellently and has no
ankit jain schrieb:
Then what to do. Is something can be done using Ctest.
We cannot guess what's in those files. Don't think about what the old
build system looks like but think about what you want to achieve.
HS
___
CMake mailing list
ankit jain schrieb:
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 make it should generate a file abc which is executable
and a script which has test cases but generated by
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:
Dmitry Bely schrieb:
On Tue, Feb 3, 2009 at 1:09 AM, Alexander Neundorf
a.neundorf-w...@gmx.net 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
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 compiler in
Am Mittwoch 18 Februar 2009 15:52:18 schrieb Bill Hoffman:
That is not the preferable way to do this. As it hard codes flags into
the CMake file. The way I would do it is:
export CXXFLAGS=-m64
export CFLAGS=-m64
export LDFLAGS=-m64
cmake ../myproject
If those environment variables are
Am Donnerstag 19 Februar 2009 07:07:27 schrieb Birju Prajapati:
-Original Message-
From: cmake-boun...@cmake.org [mailto:cmake-boun...@cmake.org] On
Behalf Of Hendrik Sattler
Sent: 18 February 2009 19:18
To: cmake@cmake.org
Subject: Re: [CMake] 64bit linking on linux
Am Mittwoch 25 Februar 2009 05:26:57 schrieb Jesse Perla:
If I add on my own value to CMAKE_CONFIGURATION_TYPES so that I can have
a separate build type in visual studio, etc. with compile time choice of
build types, then how do I change the target_link_libraries to for this new
build type?
Am Montag 02 März 2009 18:24:32 schrieb Dmytro Ovdiienko:
if I have several configurations (e.g. /MT, /MTd, /MD, /MDd), how can I
pass additional libraries to the target_link_libraries? I have two
optimized libaries. One for /MT and one for /MD.
That depends if you want to link statically or
Am Sonntag 08 März 2009 17:22:48 schrieb Andreas Schneider:
I've cross compiled libssh with mingw for windows today using the openSUSE
Build Service.
http://download.opensuse.org/repositories/home:/gladiac:/win32/win32/i586/
I'm currently trying to create a NSIS installer on Linux for libssh
Andreas Schneider schrieb:
My problem is that cmake thinks that it is a windows version...
No, it still knows that it runs on Linux and can use the native tools if
you tell it so in the toolchain file.
So you successfully *cross compile* with mingw for windows under linux and
successfully
Am Donnerstag 19 März 2009 23:03:11 schrieb Alexander Neundorf:
On Thursday 19 March 2009, Artem Zolochevskiy wrote:
hi all
I need constructive criticism for my very first CMake based project.
It converts index.txt file into html by usung asciidoc.
make install should install
Marcel Loose schrieb:
On Wed, 2009-03-25 at 15:16 +0100, Eric Noulard wrote:
2009/3/25 Marcel Loose lo...@astron.nl:
On Fri, 2009-03-20 at 16:34 +0100, Eric Noulard wrote:
2009/3/20 Marcel Loose lo...@astron.nl:
Perfect!
Ok fine.
I now use add_custom_target(check COMMAND
Marcel Loose schrieb:
On Wed, 2009-03-25 at 17:40 +0100, Hendrik Sattler wrote:
Marcel Loose schrieb:
On Wed, 2009-03-25 at 15:16 +0100, Eric Noulard wrote:
2009/3/25 Marcel Loose lo...@astron.nl:
OK, it's done.
I've added http://www.cmake.org/Wiki/CMakeEmulateMakeCheck to Specific
Topics
Zitat von Bill Hoffman bill.hoff...@kitware.com:
I have seen several requests for an autoheader type function to be
added to CMake. I have never used autoheader, but I gather it takes a
list of variables and generates a config.h.in file automatically. Does
anyone on the list have experience
Am Montag 30 März 2009 17:58:47 schrieb Bill Hoffman:
So, what would the API be? I am thinking something that you just give a
list of variables and a file name.
set(VARS HAS_A HAS_B HAS_C)
set(STRING_VARS STRING_A STRING_B)
cmake_autoheader(CMAKEDEFINE_VARS ${VARS}
Am Dienstag 31 März 2009 19:48:49 schrieb Tobias Rudolph:
add_library( iLib SHARED IMPORTED )
set_target_properties( iLib PROPERTIES IMPORTED_LOCATION /opt/local/
lib/libzip.dylib )
add_library( libFoo SHARED foo.cpp )
target_link_libraries( libFoo iLib )
According to the
Am Donnerstag 16 April 2009 19:48:03 schrieb Mike Jackson:
You will want to read this link
http://www.cmake.org/Wiki/BuildingWinDLL
[...]
PS: Feedback on that article is also welcome.
In OpenObex, we use additionally a .def file with exports. obex.sym is a list
of symbol names (one per line)
Zitat von Arjen Markus arjen.mar...@deltares.nl:
With -G MSYS Makefiles I do get the proper setting for MSYS.
The find_library command still insists on using the MS Visual C/C++
versions of the libraries, though, so I need to use my workaround
still. But at least one point is solved.
What
Zitat von Werner Smekal sme...@iap.tuwien.ac.at:
On 17.04.2009, at 10:02, Hendrik Sattler wrote:
Find_library() should only be used for libraries that are not
system or compiler specific, e.g. you look but libfoo but never for
libm.
But then cmake will complain/warn that you mix
Am Freitag 17 April 2009 20:13:40 schrieb Shaun Cummins:
Thanks, that solves one problem. I still haven't found a way to create
both shared and static libraries by only compiling the source code
once (on Linux). I can generate both types of libraries in one make
command but each source file is
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 little
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 that file
Am Montag 04 Mai 2009 16:24:29 schrieb Andreas Pakulat:
On 04.05.09 16:10:21, Hendrik Sattler wrote:
Zitat von Andreas Pakulat ap...@gmx.de:
On 04.05.09 17:56:14, ankit jain wrote:
Thanks Andreas for your reply. I already build the code using mks. now
i want to build the code using cl/VC
Zitat von roze...@volny.cz:
I would like to ask you, if (and how, if so) it is possible to set CMake
to strip (/usr/bin/strip) the generated libraries.
Hint: make help | grep strip
HS
___
Powered by www.kitware.com
Visit other Kitware open-source
Zitat von Thomas Kindler mail+cm...@t-kindler.de:
cmake tries to use cygwin-style absolute /home/tkindler.. paths,
which arm-none-eabi-gcc doesn't seem to like (being a native win32
program).
My old makefile used relative paths to invoke the compiler. How can I
do this in cmake generated
Am Donnerstag 07 Mai 2009 18:15:40 schrieb Thomas Kindler:
Hendrik Sattler wrote:
Zitat von Thomas Kindler mail+cm...@t-kindler.de:
cmake tries to use cygwin-style absolute /home/tkindler.. paths,
which arm-none-eabi-gcc doesn't seem to like (being a native win32
program).
My old
Zitat von ankit jain ankitgu...@gmail.com:
Now I am able to get all the source files from all the folders. but the
problem is that all folder source files uses one variable v1 of this Ident.c
file..
So the error iam getting while building the library is :
unresolved external symbol: v1 (iam
Zitat von ankit jain ankitgu...@gmail.com:
If suppose 5 files are there in one folder and each file uses some
functions form other file in the same folder and when ur creating library
then there is no problem..
Issue is if one folder file uses another file which is in diff. folder or in
its
Zitat von ankit jain ankitgu...@gmail.com:
Linker error for many objects files that have created
So either the object file that contains the symbol is not part of your
link command or you have a coding error.
Since you release neither an example nor further information, you will
probably
Zitat von ankit jain ankitgu...@gmail.com:
Now all files iam getting from folder1 and folder2 and objects of all files
including Ident.c is created... But while linking f11.obj f12.obj f21.obj
f22.obj all show error undefined symbol:
char *v1
where Ident .c contains..
char v1[]=Hello;
If you
Am Freitag 15 Mai 2009 17:05:58 schrieb ankit jain:
[...]
The following works with VS2008 without any problem as expected:
CMakeLists.txt:
--
project(var C)
add_executable(var sub/main.c var.c var.h)
Zitat von Mats Kindahl m...@sun.com:
I have an example case where I want to decide the subsystems to include
dynamically. However, when running CMake, I get the error above.
Anybody can tell me why I get the error and what to do about it?
You could give your files a file ending like
Zitat von Mats Kindahl m...@sun.com:
Hendrik Sattler wrote:
Zitat von Mats Kindahl m...@sun.com:
I have an example case where I want to decide the subsystems to include
dynamically. However, when running CMake, I get the error above.
Anybody can tell me why I get the error and what to do
Zitat von Mats Kindahl m...@sun.com:
Ideally, I would like to copy or build the libraries in a central lib/
directory similar to how I copy all the include files to the include/
directory, but how is that supported by CMake?
See
Hi,
either I cannot find it or it's not there: doing simple mathematic things like
substract 1 from a variable.
If that's not present, I do not understand how
LIST( LENGTH MYLIST COUNT )
FOREACH ( index RANGE ${COUNT} )
list ( GET MYLIST ${index} entry )
will address non-present indexes
Zitat von Andrew Maclean andrew.amacl...@gmail.com:
I am not sure whether this is a CMake setting or not. However we are
building an application that links against a library in /usr/local/lib
called e.g libPocoFoundation.so (this is a symbolic link to
libPocoFoundation.so.6). When we try to run
Zitat von Dmytro Ovdiienko dmitriy.ovdie...@gmail.com:
2009/5/28 Tyler Roscoe ty...@cryptio.net
But from your Lists below it appears that they don't really depend on
one another, in a target A must be built before target B sense, but
simply that they use headers from each other's source
Am Donnerstag 04 Juni 2009 20:22:12 schrieb e...@cs.bgu.ac.il:
On Thu 04 Jun 21:15 2009 Bill Hoffman wrote:
e...@cs.bgu.ac.il wrote:
On Thu 04 Jun 20:31 2009 Bill Hoffman wrote:
e...@cs.bgu.ac.il wrote:
On Thu 04 Jun 20:16 2009 Tyler Roscoe wrote:
On Thu, Jun 04, 2009 at 07:50:08PM
Zitat von bob bob...@163.com:
Hello everyone, I first used cmake, build for VS2005 and found error:
the c compiler cl is not able to complile a simple test program
why?
Did you run the shell environment for VS2005? You find the link in the
start menu.
If you did: You have to also install
Am Samstag 06 Juni 2009 04:17:43 schrieb Philip Lowman:
How would you handle target_link_libraries() and, ultimately,
find_library()? Most people using VS that would want this feature added
probably already have many of their dependencies setup with find_package()
and/or find_library().
You
Am Montag 08 Juni 2009 22:32:43 schrieb Andreas Pakulat:
On 08.06.09 22:12:00, Stefan Dröge wrote:
I solved my problem, and I think I've found a bug:
Since I'm German, my system language is set to German. Most programmes
have german console output, gcc too.
In CMakeFindEclipseCDT4.cmake
Am Montag 08 Juni 2009 23:09:17 schrieb Andreas Pakulat:
I you cannot do this for some reason: you can always choose the
translation domain with gettext and use the translated string to find the
output.
Are you sure? I don't know gettext myself, but I do know Qt's
translation mechanism
Am Dienstag 09 Juni 2009 04:20:19 schrieb Philip Lowman:
Can you try the CMakeFindEclipseCDT4.cmake attached to this bug report?
I've wrapped the call to EXECUTE_PROCESS by saving the LANG environment
variable and then setting it to C, and restoring it after running gcc.
I'm not entirely sure
Am Freitag 12 Juni 2009 21:29:00 schrieb Tyler Roscoe:
On Fri, Jun 12, 2009 at 02:42:28PM -0400, Michael Jackson wrote:
think is a kludge to get it to work. In my top level CMakeLists.txt
file I include another CMake file which calls another project via
add_subdirectory(). With in that last
Am Samstag 13 Juni 2009 00:16:43 schrieb Eric Lemings:
I've tried clearing the CMAKE_STANDARD_LIBRARIES,
CMAKE_C_STANDARD_LIBRARIES, and CMAKE_CXX_STANDARD_LIBRARIES variables
and standard libraries still get linked into my executable. How do I
disable this?
Read the compiler/linker
Am Sonntag 14 Juni 2009 22:05:14 schrieb Michael Wild:
On Mac OS X one shouldn't do this kind of detection during configure
step, because as has been mentioned a single file can be compiled
multiple times for different architectures during one single compiler
invocation. The size of void* and
Zitat von Kai Fischer fisc...@vrmagic.com:
I am cross-compiling a custom Linux ARM library with Windows XP using
the ARM toolchain from Code-Sourcery (no cygwin, mingw or anything like
that).
To accomplish that the SONAME of the library will be correctly set, I
set the VERSION property for it
Zitat von Michael Wild them...@gmail.com:
Above code for sure is far from ideal or perfect. But sometimes one
inherits a code which relies on such details, so here is one relatively
simple way to deal with it.
Agreed. But preparing old code for current reuse sometimes involves
updating it to
Hi,
FindQt4 seems to _completely_ fail for cross-compiling as it depends on
running qmake. As it finds the hosts qmake executable, all it gets is wrong
information.
Can this be solved somehow?
Thanks...
HS
___
Powered by www.kitware.com
Visit
Am Freitag 19 Juni 2009 21:13:14 schrieb Clinton Stimpson:
To cross-compile Qt apps, you still need to be able to run at least uic,
moc, and maybe other tools.
I've done it before (way back when cross-compiling support was first
added to cmake).
What I did was compile Qt for the target
Hi,
The following makes latest cmake-2.6.4 (and earlier versions) fail:
$ export CFLAGS=-Wall -Wextra -Werror
$ cmake ..
-- The C compiler identification is GNU
-- The CXX compiler identification is unknown
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler:
Am Montag 22 Juni 2009 07:54:38 schrieb Hendrik Sattler:
Same game for C++ compiler.
I must correct myself: work for C++.
HS
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource
Am Mittwoch 01 Juli 2009 18:03:10 schrieb Mark Lohry:
Apologies if this has been covered, but I'm only seeing occasional
references to doxygen in the archives.
Is there any built-in mechanism for some kind of make doc to invoke
building documentation through doxygen, or does it require
Zitat von Marcel Loose lo...@astron.nl:
On Thursday 02 July 2009 07:27:49 Hendrik Sattler wrote:
Am Mittwoch 01 Juli 2009 18:03:10 schrieb Mark Lohry:
Apologies if this has been covered, but I'm only seeing occasional
references to doxygen in the archives.
Is there any built-in mechanism
Am Sonntag 05 Juli 2009 19:36:44 schrieb du...@identicalsoftware.com:
mingw32-SDL is installed. Looking at the FindSDL.cmake and the
CMAKE_FIND_ROOT_PATH directory I can see why it doesn't find it. The
/usr/i686-pc-mingw32 directory has bin, lib, and sys-root. In
sys-root/mingw, you have
101 - 200 of 585 matches
Mail list logo
