vJc+M3j45AZ9TLu86Uwekt6Z9WAtfXtfvQGaVH5bSicz7UBopjW5oX+U+3VO83Sa
0vwSmDNbOIo7YVmjtMc4d1xJwYWsbAQ1tXnfUgk66LGZStOHzjYWhUAFoAXZGOCV
S4jiUpisEtRhtJSOkNoG
=nozd
-END PGP SIGNATURE-
From 9fd1bfa174a8c8a5e63d875492ed01e7df34d1d7 Mon Sep 17 00:00:00 2001
From: Patrick Spendrin <ps...@gmx.de>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 19.12.2015 um 01:48 schrieb digitalriptide:
> Hello,
>
> How does one select the linker and archiver for use with cmake? I
> can change my C compiler by doing this 'CC=icc cmake ..', but I
> would also like to use the Intel archiver and linker
Hi,
as I already hit this bug myself and today somebody asked on IRC again I
wanted to bring up this bug report:
http://www.cmake.org/Bug/view.php?id=11303
The problem is that cmake is a 32 bit application which by default won't
look into the 64 bit registry space. If I build a 64 bit
Am 10.07.2012 03:35, schrieb Ateljevich, Eli:
My source and tests are stored separately in a quasi-parallel arrangement:
/proj
/build
/bin # CMAKE_RUNTIME_OUTPUT_DIRECTORY
/mod1 # Build directory
/mod2
/test
/mod1
/mod2
Hi,
I just found something new for me, and wondered if this qualifies as a bug:
argv-bug.cmake
function(testfunc1)
message(STATUS testfunc1: ${ARGV0} ${ARGV1} ${ARGV2})
testfunc2(${ARGV0})
endfunction(testfunc1)
function(testfunc2)
message(STATUS testfunc2: ${ARGV0} ${ARGV1}
Am 03.05.2012 16:21, schrieb David Cole:
I think it qualifies as a bug because it's somewhat unexpected. The
question is: can we fix it without disrupting people who are
accidentally depending on this behavior
Grr.
David C.
I submitted a bug report for this:
Am 03.05.2012 16:26, schrieb Alain Leblanc:
The cmake documentation for add_subdirectory() states that the
CMakeLists files in the subdirectories should contain their own
project() command invocation. Your build file in the subdirectory does
not contain one. I don't know that it will be
Am 23.04.2012 10:45, schrieb Jörg F. Unger:
Hi everyone,
...
Any ideas how to circumvent these problems? Or is there a way to build a
64 bit cmake?
You can build 64 bit cmake with the 32 bit version and at least the
mingw-w64 compiler, it probably builds using visual studio too.
I haven't
Am 11.01.2012 21:25, schrieb David Cole:
On Wed, Jan 11, 2012 at 3:08 PM, Alexander Neundorf
a.neundorf-w...@gmx.net wrote:
On Wednesday 11 January 2012, Patrick Spendrin wrote:
Am 02.01.2012 18:11, schrieb David Cole:
Hi all,
Replies requested. Short replies only. Read on. Just a short
Am 18.11.2011 02:02, schrieb Alan W. Irwin:
Alex, is it possible your KDE Windows developers who are objecting to
pkg-config tried a version from years ago when it did not have all
these Windows issues sorted out? I suggest you tell them to
investigate again using modern pkg-config. For
Hello everybody,
we're currently thinking about setting up a symbol server for our
project, and cannot find out how to install the pdb file together with
the install command (or in another way).
Did somebody do this already? Is there only the way to fetch the pdb
files by hand?
regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Pakulat schrieb:
On 26.10.09 12:27:24, Bill Hoffman wrote:
Andreas Pakulat wrote:
But that should be the case if I start kdevelop from a cmd.exe that had
vcvars32.bat called. However it seems that executing cmake still fails when
spawned
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dominik Szczerba schrieb:
BTW do you know if it is possible to do a parallel build with nmake?
(like -jN with GNU make)
It isn't.
A replacement tool has been developed though:
Philip Lowman schrieb:
Hi,
Luigi suggested a kind of CMake ports system in a recent thread here on
the CMake mailing list. This would presumably be a system whereby
popular 3rd party dependencies which have not yet CMakeified their
source trees could be CM'd and baselined in one place and
Jon Shuler schrieb:
Right now we have a build\win32 directory that contains all the projects
files. I was looking at creating a CMakeLists.txt for each project and
putting them in the same directory. I rather have separate
CMakeLists.txt for each project instead of one big file.
How would
Hello,
after speaking with Alex Neundorf I am asking here to reach more ppl.
My problem:
When I build a library foo and export it with install(EXPORT) etc. I
will get a file called foo.cmake and foo-Debug.cmake which should be
included when developing with my library foo. So if I now take the
Hello,
as I am just working with some boost headers that do reside in a
different include directory, I would like to ask to apply the appended
patch.
It will not only find versions where headers are in
prefix/include/boost/boost_1_34 (which is currently the default for
windows) but also
17 matches
Mail list logo