I don't think it is possible to find both required and optional
libraries with the same find_package command. Is that true?
I have a installation of Boost which has a proposed library added into
it called Boost.Log ('log' for short). I require the
boost_program_options library but optionally can u
On 08/07/2010 03:52 AM, Verweij, Arjen wrote:
> Apparently it breaks because of /INCREMENTAL:YES --
Interesting. It works for ifort 11.1. So does
ifort /incremental:yes myfile.f
ICE for any file with ifort 9.1?
> Can I just turn this off in Windows-ifort.cmake or is this
> symptomatic of an
Hi,
>Interesting. It works for ifort 11.1. So does
>
> ifort /incremental:yes myfile.f
>
>ICE for any file with ifort 9.1?
Hrm, no not really :|
Not too sure why this is breaking. Is this technically an ICE? I see ifort
reporting it, but it occurs when linking and both ifort and xilink call
Hi,
I'm investigating a problem where on 64-bit Windows the generated build.make
(NMake or NMake JOM) does not make use of response files. I have tried
transplanting the settings file for the 32 bit platform and minimizing
differences, but still I cannot get it to use rsp files. This is a probl
Patch attached :P
Arjen
Windows-ifort.cmake.patch
Description: Windows-ifort.cmake.patch
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and c
On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
> 2010/8/4 Kishore :
> > On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote:
> >> Hi All,
> >>
> >> I did add a patch for the "multiple file problem"
> >> http://public.kitware.com/Bug/view.php?id=10736
> >>
> >> May be interested people can h
On 8/9/2010 11:49 AM, Verweij, Arjen wrote:
Hi,
I'm investigating a problem where on 64-bit Windows the generated build.make
(NMake or NMake JOM) does not make use of response files. I have tried
transplanting the settings file for the 32 bit platform and minimizing
differences, but still I c
Brad,
I have access to the machine again. I've tried another approach. What do you
make of this? I'm sure you know what cmake -E vs_link_exe is supposed to do. :)
The first works, the second does, even with /INCREMENTAL:YES
Regards,
Arjen
ACCORDING TO build.make:
E:\trycompile\CMakeFiles\CMak
Hi Bill,
>> I'm also unsure why in one case the linking is done through link.exe and by
>> lib in the other.
>One is using visual studio, and one is using the intel compiler. They
>have different files in the Platform directory. That is why they can be
>different. See Windows-icl.cmake.
Than
On 8/9/2010 12:31 PM, Verweij, Arjen wrote:
Brad,
I have access to the machine again. I've tried another approach. What do you
make of this? I'm sure you know what cmake -E vs_link_exe is supposed to do. :)
The first works, the second does, even with /INCREMENTAL:YES
Regards,
Arjen
ACCORDING
On 08/09/2010 12:39 PM, Verweij, Arjen wrote:
> Both link rules for static libraries however do not contain
> ${CMAKE_START_TEMP_FILE} or ${CMAKE_END_TEMP_FILE} yet one platform I end
> up with objects1.rsp but on the other the lists of objects are passed as
> arguments to lib. Is there some implic
On 8/9/10 12:11 PM, Kishore wrote:
> On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
>> 2010/8/4 Kishore :
>>> On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote:
Hi All,
I did add a patch for the "multiple file problem"
http://public.kitware.com/Bug/view.php?id=10736
>>
2010/8/9 Chris Wolf :
>
>
> On 8/9/10 12:11 PM, Kishore wrote:
>> On Friday 06 Aug 2010 4:18:36 am Eric Noulard wrote:
>>> 2010/8/4 Kishore :
On Monday 02 Aug 2010 4:59:47 pm Eric Noulard wrote:
> Hi All,
>
> I did add a patch for the "multiple file problem"
> http://public.kit
Hello,
I'm using CMake for Visual Studio as well as Makefiles for Linux. In
windows, debug and release directories seem to be added for the executables.
I actually would like to do three things:
1) Test for a debug or release build
2) Name the executable created based on it's build. (myProgram_d
Sorry, meant to keep this on the list.
- Ben
-- Forwarded message --
From: Ben Medina
Date: Mon, Aug 9, 2010 at 12:45 PM
Subject: Re: [CMake] Eliminate Debug/Release directories and name
executables based on configuration
To: James Ihrig
I believe this is what the DEBUG_POSTFIX
What you need to do to get rid of the Debug/Release directories is set the
prefix property for your target with "../".
Eg. set_target_properties( target_name PROPERTIES PREFIX "../" )
To get a postfix for different configuration types you need to set the postfix
property for the build
>> Well, I don't think there's a way around it. But you can use a loop to do
it:
Ok good to know.
>> Another thing, though: Never, ever, configure a file into the source
tree. Doing so is a recipe for disaster...
Curious as to why.
This is exactly what I am doing so I can run matlab among other
Hi all.
I wrote some unit tests for a library target in my project. A driver
application links the library and runs the tests. This works fine with
Makefile targets on Linux. With MinGW Makefiles on Windows, the driver
properly links, but when running `make test`, the system complains that it
You could set this target property:
http://cmake.org/cmake/help/cmake-2-8-docs.html#prop_tgt:RUNTIME_OUTPUT_DIRECTORY
Or this variable prior to defining any targets:
http://cmake.org/cmake/help/cmake-2-8-docs.html#variable:CMAKE_RUNTIME_OUTPUT_DIRECTORY
...to put all the runtime (exe and dll) out
HI, ALL
hiphop-php needs cmake to compile, but I got this error when running make :
--
[r...@s
2010/8/10 a qi :
> HI, ALL
>
> hiphop-php needs cmake to compile, but I got this error when running make
> :
May the right place to ask for that would be the HipHop PHP Mailing list?
http://groups.google.com/group/hiphop-php-dev/?pli=1
---
Hi,
I come back to know if anyone have an idea of howto do this tricks ?
Thanks.
Vincent
On Fri, Jul 23, 2010 at 09:44, Vincent LEFORT wrote:
> Hello, i use CPack to pack my project.
>
> I use components (cpack_add_component) in it, and i do some links in start
> menu using "set(CPACK_NSIS_MEN
22 matches
Mail list logo