Hi,
On Mon, Nov 5, 2012 at 5:47 PM, Bill Hoffman wrote:
> On 11/5/2012 8:31 PM, Matthew Brett wrote:
>>
>> Is there something else I can do to find out where the problem is?
>
> make VERBOSE=1 with both and see what the difference is with the link lines.
Thanks for the hint.
Output of 2.8.10 co
On 11/5/2012 8:31 PM, Matthew Brett wrote:
Is there something else I can do to find out where the problem is?
make VERBOSE=1 with both and see what the difference is with the link lines.
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
http://www.
Hi,
On Mon, Nov 5, 2012 at 12:44 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Nov 5, 2012 at 7:57 AM, Brad King wrote:
>> On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
>>> The problem is in commit e7e613e. Patching Darwin.cmake back to revision
>>> 43b74793 solves the problem.
>>>
>>> The bre
I have a project that occasionally says it cannot access it's .ilk file;
but rerunning the build and it works usuaully... but it's only that one
project that has the problem, and an incremental link file is only for that
project
On Mon, Nov 5, 2012 at 3:49 PM, Todd Greer wrote:
> I'll ask my tea
I'll ask my team about what circumstances it's been hit in, but I would expect
a permission error to happen every time, whereas this failure is intermittent.
-Original Message-
From: rcdai...@gmail.com [mailto:rcdai...@gmail.com] On Behalf Of Robert Dailey
Are you on Windows Vista or hig
Sorry I got confused, what I needed to use is CMAKE_CFG_INTDIR.
On Mon, Nov 5, 2012 at 5:17 PM, Robert Dailey wrote:
> I'm using a custom target to copy files to the following directory:
>
> ${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$
>
> This works on Visual Studio generators, because binaries that are
Are you on Windows Vista or higher? If so, have you tried running
Visual Studio as Administrator and doing a build? I don't have this
problem, but my first thought was that maybe you are having some
permissions errors. I also have several targets that build in parallel
in the same directory.
On Mo
I'm using a custom target to copy files to the following directory:
${CMAKE_RUNTIME_OUTPUT_DIRECTORY}/$
This works on Visual Studio generators, because binaries that are
compiled are placed in the directory above.
However, if I generate for NMake on Windows, binaries are placed in
${CMAKE_RUNTIM
I have several libraries in my build that are declared in the same
CMakeLists.txt (by add_library). Unfortunately, the Visual Studio generator
(2010, but I don't think it matters) puts "CMakeFiles\generate.stamp" in the
output directory for that CMakeLists.txt. Unless I'm mistaken, when being bu
On Nov 5, 2012, at 12:44 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Nov 5, 2012 at 7:57 AM, Brad King wrote:
>> On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
>>> The problem is in commit e7e613e. Patching Darwin.cmake back to revision
>>> 43b74793 solves the problem.
>>>
>>> The breakage i
Hi,
On Mon, Nov 5, 2012 at 7:57 AM, Brad King wrote:
> On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
>> The problem is in commit e7e613e. Patching Darwin.cmake back to revision
>> 43b74793 solves the problem.
>>
>> The breakage is here:
>> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e
Thanks Alex,
I am using ExternalProject_Add() to add websocketpp to my build and it
generates the library libwebsocketpp.a fine.
My question is what is the standard way that other CMAKE projects would locate
the library for linking?
Thanks,
Rob
-Original Message-
From: Alexander Neundo
Is there a way to make CMake's copy and copy_if_different CMD commands
output verbose copy information?
Something like:
Copying foo.txt...
Copying bar.txt...
If not, is there a way to utilize a custom command in CMake script to
conditionally echo if copy_if_different actually ends up copying a
On Monday 05 November 2012, Mike Krus wrote:
> Hi again
>
>
> Using ASM_NASM works better except the nasm call seems to get all the CXX
> flags, some of them (-F) being invalid.
This is what is being set in Modules/CMakeASM_NASMInformation.cmake, which
should be used:
set(CMAKE_ASM_NASM_COMPI
On Monday 05 November 2012, Mike Krus wrote:
> Hi
>
> got some issues compiling ASM of Mac, mixed with other C++ code. In my
> CMake file I use:
>
> INCLUDE(CheckLanguage)
>
> check_language(ASM)
>
> if(CMAKE_ASM_COMPILER)
>
> enable_language(ASM)
>
>
On Monday 05 November 2012, Marshall, Rob wrote:
> Is the intent of the find_package() macro to be used to locate prebuilt
> third party libraries that have Include and library files prebuilt?
>
> Or can it be used in a scenario where third party source is on the local
> file system but will be bu
On Monday 05 November 2012, Mike Krus wrote:
> Hi
>
> got some issues compiling ASM of Mac, mixed with other C++ code. In my
> CMake file I use:
>
> INCLUDE(CheckLanguage)
>
> check_language(ASM)
>
> if(CMAKE_ASM_COMPILER)
>
> enable_language(ASM)
>
>
Hi again
Using ASM_NASM works better except the nasm call seems to get all the CXX
flags, some of them (-F) being invalid.
FAILED: /usr/bin/nasm -Iproducts/4DMove/tools/sediment
-I../../products/4DMove/tools/sediment -I../../products/4DMove
-I../../products/4DMove/utilities -Iproducts/4DMove
Hi
got some issues compiling ASM of Mac, mixed with other C++ code. In my CMake
file I use:
INCLUDE(CheckLanguage)
check_language(ASM)
if(CMAKE_ASM_COMPILER)
enable_language(ASM)
LIST(APPEND nm_tls_ALL_src src/FlowScalarField64.asm)
On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
> The problem is in commit e7e613e. Patching Darwin.cmake back to revision
> 43b74793 solves the problem.
>
> The breakage is here:
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7e613efbf1da45a2a9e51d11a4022589d79c642
Thanks for tracking
2012/11/5 Bogdan Cristea :
>
> On Monday 05 November 2012 13:57:04 you wrote:
>> There seems to be relatively recent commit in the repository though:
>> http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/
>
> The latest release is 2.46, December 2009. I have not tried yet the version
> from tru
On Monday 05 November 2012 13:57:04 you wrote:
> There seems to be relatively recent commit in the repository though:
> http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/
The latest release is 2.46, December 2009. I have not tried yet the version
from trunk, but I have noticed in Win8 some
2012/11/5 Bogdan Cristea :
> Hi
>
> NSIS seems to be quite outdated and no longer developed,
There seems to be relatively recent commit in the repository though:
http://nsis.svn.sourceforge.net/viewvc/nsis/NSIS/trunk/
there is some evolution there as well:
http://code.google.com/p/unsis/
> are
Hi
NSIS seems to be quite outdated and no longer developed, are there any plans
to suppport new installer systems on Windows (e.g. the ones provided by Visual
Studio) ?
regards
--
Bogdan
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensou
24 matches
Mail list logo