On 03/09/2015 02:50 PM, Roman Wüger wrote:
if CMake 3.2.0 will not be released, when is the expected release date for
CMake 3.2.1?
Technically 3.2.0 has been released (there is a signed tag in
the source tree for it, created after a drought in feedback
on 3.2.0-rc2). We just never published
On 03/06/2015 06:57 AM, Nils Gladitz wrote:
On 03/06/2015 10:22 AM, Pere Mato Vila wrote:
[100%] [100%] *Generating A.txt, B.txt*
*Generating A.txt, B.txt*
Thanks for trying the release candidate and reporting this.
This seems to be the case since
[644b4688d71cc52f8499d6103495de0909319557]
On 03/11/2015 05:22 PM, Roman Wüger wrote:
This simple example produces the following error on Mac OS:
error: cannot initialize a parameter of type 'bool *' with an rvalue of type
'void *'
void doSomething(int n = 1, bool *ok = static_castvoid*(0)) {
^
On Tue, Mar 17, 2015 at 12:10 AM, Dave Yost wrote:
set_source_files_properties(foo.bar PROPERTIES LANGUAGE CXX)
[snip]
[100%] Building CXX object CMakeFiles/foo.dir/foo.bar.o
c++: warning: /Users/yost/p/c++/cmake/asm/foo.bar: linker input file unused
because linking not done
Linking CXX
On 03/25/2015 10:15 AM, Roger Leigh wrote:
Question: Why is TESTDIR2 transformed from t2 to
/home/rleigh/pathtest/test/t2 (which is
$PROJECT_BINARY_DIR/$TESTDIR2)?
It looks like the behavior has been this way since 2003:
ENH: When fixing cache value with uninitialized type, collapse
full
On Tue, Mar 24, 2015 at 11:03 PM, Hugh Sorby wrote:
I am trying to create a simple Fortran project that relies on a module file
that has been built by another project. I have added the directory
containing the module file into the include_directories command but the
project isn't compiling
On 03/25/2015 08:26 PM, Hugh Sorby wrote:
|-- ex
| |-- CMakeLists.txt
| `-- use_mod.f90
|-- ex-build
|-- install
|-- modsrc
| |-- CMakeLists.txt
| `-- a.f90
`-- modsrc-build
Thanks for the detailed example. It was trivial to reproduce the
issue with that!
Since this commit:
On 02/25/2015 01:58 PM, Zaak Beekman wrote:
When multiple executables or libraries depend on the same
fortran source file that contains a module, parallel (Makefile)
builds are failing for me because the .mod file is getting
moved/renamed/written by more than one process at a time. Is
there a
On 05/01/2015 02:56 AM, Arjen Markus wrote:
On 04/30/2015 06:04 PM, Nikolaus Rath wrote:
I am not sure why CMake is trying to copy module files around
It is copying the module to a timestamp file so that dependents
don't have to rebuild if the module content didn't really change.
Even if CMake
On 05/01/2015 06:25 AM, Alan W. Irwin wrote:
# First call to project so that CMAKE_SYSTEM_NAME is defined
project(plplot NONE)
if(CMAKE_SYSTEM_NAME STREQUAL Linux)
cmake_minimum_required(VERSION 3.0.2 FATAL_ERROR)
else(CMAKE_SYSTEM_NAME STREQUAL Linux)
On 05/07/2015 11:00 AM, Wim Bekker wrote:
I've just downloaded and installed the 3.2 QtHelp documentation.
Every topic I choose comes with a page Host www.google-analytics.com
not found.
That was a problem with the way the file was generated that is now
fixed. Please download a fresh copy
On 05/17/2015 12:35 AM, Taylor Braun-Jones wrote:
CMake already has an ENVIRONMENT property for tests ...
symmetric feature would be to support an ENVIRONMENT property
for targets as well.
We can provide it for tests because ctest directly runs the tests.
There is no way to implement
On 05/15/2015 02:26 PM, Alan W. Irwin wrote:
function(plplot_cmake_minimum_required)
cmake_minimum_required(${ARGV})
endfunction(plplot_cmake_minimum_required)
Help: Document behavior of cmake_minimum_required in a function
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e5f8ead5
-Brad
On 04/14/2015 12:25 PM, Bartlett, Roscoe A. wrote:
Is there a way to make CMake flush STDOUT
Not from the CMake language. However, it shouldn't matter.
This is a problem since I have tests that grep output generated
[snip]
to point to the inc-- Configuring incomplete, errors occurred!
On 4/17/2015 8:44 AM, Jon Hodgson wrote:
The CXX compiler identification is AppleClang 5.1.0.5030040
The C compiler identification is AppleClang 5.1.0.5030040
Good.
But then it bombs out at the line
PROJECT(${PROJECT_NAME} CXX C)
with the error
No CMAKE_CXX_COMPILER could be found
On 04/10/2015 12:26 PM, Robert Dailey wrote:
I am noticing that after installing the official Windows installer for
3.2.1 release, CMake GUI looks different. Menu options have GCC
specific options and when I generate through the GUI for Visual Studio
2013, my projects are missing preprocessor
On 06/17/2015 11:07 AM, Ette, Anthony (CDS) wrote:
Please see the response below about uniquely identifying cf77.
In order to identify the compiler as cf77, do something akin to the following:
$ echo ' PROGRAM V' /tmp/nil.f
$ echo ' END' /tmp/nil.f
$ cf77 -v -o /dev/null -c
On 06/18/2015 08:44 AM, Brad King wrote:
We may be able to extract that while compiling the compiler identification
source file. Try modifying Modules/CMakeDetermineFortranCompiler.cmake
and extending the list in CMAKE_Fortran_COMPILER_ID_TEST_FLAGS with -v.
Then run CMake on the tiny
On 06/18/2015 04:01 PM, Ette, Anthony (CDS) wrote:
rts1-4:/home/bzpl46/test2 cmake -G Unix Makefiles
-- The Fortran compiler identification is CCur
-- Check for working Fortran compiler: /usr/ccs/bin/cf77
-- Check for working Fortran compiler: /usr/ccs/bin/cf77 -- works
Great! Thanks for
On 06/20/2015 04:10 AM, Roman Wüger wrote:
but the problem with this command is, that for multi configuration
environments (e.g. Visual Studio), it requires $CONFIG in the
filename which then creates 4 header files. One for each configuration.
Yes, because generator expressions can reference
On 06/16/2015 09:31 AM, Ette, Anthony (CDS) wrote:
rts1-4:/home/bzpl46/test2/CMakeFiles/CMakeTmp /usr/ccs/bin/cf77
CMakeFiles/cmTryCompileExec3453195864.dir/testFortranCompiler.f.o -o
cmTryCompileExec3453195864 -rdynamic
/usr/ccs/release/7.3/lib_ia32/ld: cannot find -lrt
That shows it can
On 06/16/2015 01:21 AM, Ette, Anthony (CDS) wrote:
what control does the user have over the compilation of the test program?
Very little. The whole point is to test that the compiler works the way
CMake will invoke it in the generated build system.
I.e. can I tell cmake to add -L (where to
On 06/16/2015 10:00 AM, Ette, Anthony (CDS) wrote:
That shows it can be reproduced locally outside of CMake.
Please try dropping -rdynamic from that command line.
Ahh, you are correct. Success! What does this mean?
This means CMake needs to be able to define and detect an
id for this
On 06/12/2015 07:19 AM, Roman Wüger wrote:
It would be great if generator expressions can be used with
configure_file to avoid such overhead.
Does anyone have an idea on how to solve that?
See file(GENERATE).
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check
On 06/16/2015 01:44 PM, Ette, Anthony (CDS) wrote:
I'm still struggling getting anything unique from the cf77 command line.
What is the output of cf77 --version?
Okay, the -rdynamic option to cf77 instructs it to build
a shared object (shared library), not an executable program.
That may be
On 06/15/2015 01:53 PM, Ette, Anthony (CDS) wrote:
Thank you for the response. I suppose I should've provided
more information about the platform up front. Our system is a
RHEL5 variant named RedHawk Linux. The kernel is a custom
real-time kernel developed by Concurrent Computer Corporation
On 06/15/2015 11:31 AM, Ette, Anthony (CDS) wrote:
Any ideas? Our FORTRAN compiler (Concurrent Computer Corporation
port of f77) is failing to compile simple test program because the
linker can't find -lrt
From the log:
/usr/ccs/bin/cf77 -c
On 06/15/2015 03:42 PM, Ette, Anthony (CDS) wrote:
you mention that it is my responsibility to setup the environment
before invoking Cmake and while I agree, it's just not clear to me
what speficially Cmake requires to be setup.
The environment is not for CMake but for the compiler itself. I
On 06/15/2015 03:08 PM, Ette, Anthony (CDS) wrote:
Okay. If -lrt is the default for the compiler why might rt not be found?
say if one of my CMakeFiles.txt had SET(CMAKE_CXX_LINK_FLAGS -lrt))
or are my CMakeFiles.txt not considered as part of building a simple
test program?
Some information
On 06/01/2015 04:38 PM, david_bjorn...@keysight.com wrote:
Deterministically generating a GUID sounds like a real solution.
If I get a chance I'll look at whether CMake can deterministically
generate a GUID from a hash of the build tree and target names
I've done this here:
VS: Compute
On 05/28/2015 01:32 PM, lucas.pet...@engilitycorp.com wrote:
It is interesting to note that the stdc++ library is in
CMAKE_C_IMPLICIT_LINK_LIBRARIES and CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES
but not in CMAKE_CXX_IMPLICIT_LINK_LIBRARIES.
A similar case was discussed here:
On 05/31/2015 12:43 PM, Dan Kegel wrote:
Did you try the workaround suggested in the first link you gave, i.e.
set( RatherLongLibraryName_GUID_CMAKE generated GUID CACHE INTERNAL
remove this and Visual Studio will mess up incremental builds)
On Sun, May 31, 2015 at 9:04 AM,
On 05/21/2015 06:00 PM, lucas.pet...@engilitycorp.com wrote:
I am trying to compile a code written in C, but using an external
library that contains C++ functions. I am on a Cray system and
everything works if I manually link with the cray CC wrapper.
When I change the linker language with
On 05/26/2015 02:23 PM, Mark Lakata wrote:
CMake Error: Remove failed on file:
/.../CMakeTmp/.nfs0786c4ec398c:
System Error: No such file or directory
I'll work on changes to teach CMake to tolerate ENOENT here in
case it loses a race like this.
Thanks,
-Brad
--
On 05/27/2015 01:24 PM, Brad King wrote:
On 05/26/2015 02:23 PM, Mark Lakata wrote:
CMake Error: Remove failed on file:
/.../CMakeTmp/.nfs0786c4ec398c:
System Error: No such file or directory
I'll work on changes to teach CMake to tolerate ENOENT here in
case
On 07/02/2015 05:06 PM, Clifford Yapp wrote:
When running the BRL-CAD configure process with the latest CMake
release candidate, the first configure pass completes successfully.
The second pass fails almost immediately with the error:
CMake Error at CMakeLists.txt:120 (configure_file):
On 07/27/2015 03:26 PM, Roman Wüger wrote:
SubProj1 and SubProj2 does not find mutex, but
check_cxx_source_compiles succeeds.
Did I miss configure something here?
The posted example works for me on Linux with g++ 4.9.3.
The check succeeds and an executable I create in SubProj1
can #include
On 07/28/2015 12:51 PM, Bill Somerville wrote:
The possible lack of grep is a potential issue so your read
back from file suggestion is interesting, is there a recognized place to
write temporary files like this?
IIRC the code in question runs during cmake -P cmake_install.cmake
scripts so
On 07/28/2015 11:32 AM, Bill Somerville wrote:
I have checked for objdump command options to reduce the output but
there don't appear to be any that help. TBH running from the command
line as, for example:
$ objdump -p executable | grep 'DLL Name:'
runs in a fraction of a second
On 07/28/2015 12:23 PM, Roman Wüger wrote:
I've tried it on Mac OS 10.10.4 with clang 6.1.0.6020053 from
XCode 6 using Unix Makefiles as the generator.
Is that using the Xcode Command Line Tools or the /usr/bin/c++ stub that
uses the /Applications/Xcode.app/.../bin/clang++ compiler underneath?
On 07/21/2015 06:16 PM, Roman Wüger wrote:
I've attached a patch which learns CTest to handle it.
I hope this patch could be merged.
Good start. Please also update Help/manual/ctest.1.rst with
documentation for the new options. Also please extend the test
suite, likely in
On 07/20/2015 03:45 PM, Berteun Damman wrote:
Note that it displays the full path for foo.txt! With later CMake
versions (3.1 and up is my suspicion), it will display:
build$ cmake ..
foo.cc
foo.txt
I tried looking trough the release notes, and I've found that
add_library gained support
On 07/20/2015 05:10 PM, Allen Byrne wrote:
We use the OBJECT_DEPENDS property as follows;
Environment: Windows 7, Visual Studio 2012, Intel Fortran 15, and CMake 3.1
It looks like OBJECT_DEPENDS is not fully implemented for VS = 10.
I'll look at fixing that.
Meanwhile you can work around the
On 07/21/2015 01:06 PM, Brad King wrote:
It looks like OBJECT_DEPENDS is not fully implemented for VS = 10.
I'll look at fixing that.
It turns out that is because .vcxproj files do not support it.
The ClCompile task is documented here:
https://msdn.microsoft.com/en-us/library/ee862477.aspx
On 07/14/2015 12:57 AM, Andrew Maclean wrote:
This patch fixes this warning when building CMake from the master:
WARNING: 'default' html theme has been renamed to 'classic'.
Applied with slight tweaks:
Utilities/Sphinx: Use 'classic' theme for Sphinx = 1.3
On 07/21/2015 04:12 AM, Roman Wüger wrote:
Is there a way to get the full output without modifying every
CMake Script of about ~ 35 projects?
CTest always truncates the output of passing tests unless the
test output contains the literal text CTEST_FULL_OUTPUT.
This was done long ago to limit
On 07/14/2015 01:13 PM, Brad King wrote:
Applied with slight tweaks:
Utilities/Sphinx: Use 'classic' theme for Sphinx = 1.3
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e59a7d7e
[snip]
On 07/14/2015 06:56 PM, Andrew Maclean wrote:
Thanks, that looks much better than what I did!
I had
On 10/07/2015 12:45 PM, Orion Poplawski wrote:
> There also appears to be a similar issue with building Paraview where the
> MPI_INLCUDE_PATH is no longer being passed to the compile line.
Can you provide any more detail on this problem? There was only one
change to FindMPI between 3.3.2 and
On 10/22/2015 11:28 AM, Orion Poplawski wrote:
>>> This appears to have broken plplot's ada build on Fedora.
>
> FYI - builds still fail with cmake 3.4.0-rc2. Have had time to look at it
> closer. plplot issue seems to be triggered by a change in Ada_FLAGS:
>
> -Ada_FLAGS =
>
On 10/26/2015 02:52 PM, Federico Milano wrote:
> but the only way I have made it work is by uninstalling Git.
[snip]
> Do you know what command is run when it is printing the line "Found Git:..."?
By the time that prints then most of the Git operations should be finished.
Run "cmake" from the
On 10/29/2015 10:33 AM, Sylvain Joubert wrote:
> I recently upgraded to CMake >= 3.3 and I get a CMP0058 warning on some
> of the generated files. What I don't understand is that:
> - These files are not generated at build time but at configure time,
> why can't they just be seen as regular
On 11/03/2015 03:54 PM, Martin Weber wrote:
> The download site [1] seems to have been revamped. Since then, it does no
> longer allow to download older releases.
The directory index was disabled but old direct links should still have worked.
> If the devs decided to disable directory listings
On 07/08/2015 10:58 AM, Ghyslain Leclerc wrote:
I think I have found a bug in CMake and as suggested in the
Mantis Bug Tracker, I am writing here on the list before
actually filing the bug report in case it’s actually not a bug.
I have also searched in the already filed bugs for a few minutes
On 07/09/2015 01:43 PM, Clifford Yapp wrote:
OK, more info - it looks like the problem is limited to the CMake GUI
configure (although I haven't been able to test ccmake, the basic
cmake works) and the test file is pretty simple:
Thanks. I've narrowed it down to this session:
On 08/27/2015 03:24 AM, Daniel Wirtz wrote:
CMake 3.3.0.
[snip]
after checking, the @CMakeFiles/VerifyFortranC.dir/linklibs.rsp does not
contain the -lgfortran library include, hence the fuss.
I managed to reproduce this and track down the problem. Here
is a fix based on 3.3.1:
Makefile:
On 9/4/2015 10:17 AM, André Netzeband wrote:
> I have a very strange issue with generated nmake makefiles from cmake 3.3.1
Is this problem new in 3.3 or are you just reporting this as the version
you are using?
> In a very complex project with many sub-cmake files (Ogre3D) the
> generated nmake
On 09/15/2015 05:53 AM, Daniel Wirtz wrote:
> because cmake did not add the "-std=c99" c flags.
> so has that simply not come up yet or is there a reason cmake does not
> add those flags for intel?
The necessary tables of information have simply not been filled out
for the Intel compiler. No
On 09/27/2015 08:47 PM, Michael Catanzaro wrote:
> CMake Warning (dev):
> Policy CMP0058 is not set: Ninja requires custom command byproducts to be
> explicit. Run "cmake --help-policy CMP0058" for policy details. Use the
> cmake_policy command to set the policy and suppress this warning.
On 09/18/2015 02:42 PM, Bill Newcomb wrote:
> Suppose I add a library in my project:
>
> add_library(foo STATIC foo.c bar.c)
>
> Is there a way I can get the name of the generated library file at
> configure time?
On multi-configuration generators like VS and Xcode there may be
more than one
On 09/22/2015 09:25 AM, Tom Kacvinsky wrote:
> I am using cmake 2.8.11.2 on Windows 7 with Visual Studio 2008
[snip]
> whether listing the object files or compiling from source, there is
> the cl option to create PDB debugging information.
Please try with CMake 3.1 or higher:
On 09/22/2015 11:16 AM, Tom Kacvinsky wrote:
> having two builds (debug and release) doesn't fit our workflow
Try using the RelWithDebInfo configuration.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
On 10/01/2015 04:07 AM, Roman Wüger wrote:
> set_target_properties(${PROJECT_NAME} PROPERTIES FRAMEWORK TRUE)
>
> Is there a way to rename the suffix ".framework"?
Not currently. It is hard-coded here:
On 12/04/2015 02:12 AM, Vasily Vladimirovich Vylkov wrote:
> Thanks all -- that worked. The key:
> regedit.exe --> HKLM\SYSTEM\ControlSet001\Control\Environment\Path
>
> had a backup of the path var before the CMake install nuked it.
>
>> How long was your PATH before?
>
> Just my luck, it
On 12/04/2015 05:51 PM, Zaak Beekman wrote:
> What are the pros and cons of using FindMPI over passing FC=mpif90 and
> CC=mpicc?
It shouldn't matter much if all the code in the project is meant
to be build for MPI. Using plain FindMPI with the CC/CXX/FC set
to the system compilers is cleaner
On 12/03/2015 11:04 AM, Vasily Vladimirovich Vylkov wrote:
> Installing CMake on Windows (7, 64-bit) with the "add cmake to system
> PATH for all users" option overwrote the contents of my PATH variable,
> instead of appending to it. This is horrible! I don't know of any
> way to recover my
On 12/01/2015 02:41 PM, Dan Liew wrote:
>> Perhaps, but after regenerating the project the build tool will not
>> re-load the build files and start building again. That will take
>> an additional invocation. The number of iterations required is
>> bounded only by the depth of dependency chains.
On 12/04/2015 02:14 PM, Johnson, Hans J wrote:
> PERFORM_CMAKE_TEST(vxl_platform_tests.cxx VCL_STATIC_CONST_INIT_FLOAT)
> NOTE: THIS FAILS WHEN IT SHOULD PASS!
[snip]
> Should I simply add -DCMAKE_CXX_STANDARD:STRING=${CMAKE_CXX_STANDARD}
> to the TRY_COMPILE? The seems too simplistic.
I think
On 12/09/2015 10:06 PM, Alan W. Irwin wrote:
> Also, the documentation of the ctest --timeout option says:
>
> `--timeout `
> Set a global timeout on all tests.
>
> This option will set a global timeout on all tests that do not
> already have a timeout set on them.
Yes, one can see that
On 12/07/2015 09:06 AM, Brad King wrote:
> Yes. We will look at addressing this for the 3.5 release now that we
> understand the cause.
We've switched to using the WiX generator to produce a .msi installer
instead:
Utilities/Release: Switch to .msi builder for Windows binary
https://cma
On 11/30/2015 01:56 PM, Dan Liew wrote:
> It doesn't look completely impossible. For Ninja, it looks like it has
> some support for compiler generated dependency files [2]
Yes, it may be possible for Ninja.
> There is an alternative which I suggested in the post. Have CMake
> determine the
On 11/30/2015 01:32 PM, Dan Liew wrote:
> It works but only for makefile generators... That's an annoying
> limitation. I'll file a feature request to get this implemented for
> other generators.
It happens to work for Makefile generators because it was easy to
implement since those generators
On 06/08/2016 06:02 PM, Gonzalo Garramuño wrote:
> I tried v3.6.0 rc1 but it fails on linking with a message about unknown
> symbols when doing cmake -E vs_link_dll on a windows library. It seems
> not to recognize the symbols in, for example, tinyxml2.
>
> The same code works just fine under
On 06/07/2016 10:58 AM, Lowekamp, Bradley (NIH/NLM/LHC) [C] wrote:
> I tried out the 3.6.0-rc1 and my problem building CMake still exists.
Thanks for testing it.
> (cd /tmp/cmake-build && \
> ../cmake-3.6.0-rc1/bootstrap && \
> make -j 10 && \
> ./bin/cmake
On 06/07/2016 04:00 PM, Kristian wrote:
> What's the meaning of the bootstrap executable? I thought, when
> compiling CMake, it is sufficient to call ./configure and then make...
The bootstrap script is the way to bootstrap CMake. The `configure`
script is just a thin wrapper around `bootstrap`
Hi Folks,
CMake issue tracking is now hosted on Kitware's GitLab instance:
https://gitlab.kitware.com/cmake/cmake/issues
The old mantis issue tracker will remain available as a read-only
reference. All CMake issues from that tracker have been migrated
to the new CMake Issues page with their
On 06/13/2016 02:58 PM, Roman Wüger wrote:
> I have successfully configured a project with CMake 3.5.2 so it
> creates a valid Release and Debug *.app bundle which runs on iOS.
> However if I build an archive in Xcode with "Product->Archive"
> then the app bundle seems not complete under
>
On 01/11/2016 10:49 AM, Alan Burlison wrote:
> So is the answer here to add -m64 just to CMAKE_EXE_LINKER_FLAGS and
> CMAKE_SHARED_LINKER_FLAGS and not to CMAKE_STATIC_LINKER_FLAGS? Are
> CMAKE_STATIC_LINKER_FLAGS only ever used with ar?
Yes and yes. Actually adding -m64 to CMAKE_{C,CXX}_FLAGS
On 01/11/2016 09:42 AM, Alan Burlison wrote:
> The "-m64" flag is used to tell the compiler/linker to create 64-bit
> executables and is set via the following CMake variables:
>
> CMAKE_EXE_LINKER_FLAGS
> CMAKE_SHARED_LINKER_FLAGS
> CMAKE_STATIC_LINKER_FLAGS
What is adding -m64 to
On 01/11/2016 11:53 AM, Alan Burlison wrote:
> ISTR part of the issue at least was in the bowels of the CMake FindJNI
> module, that makes extensive use of CMAKE_SYSTEM_PROCESSOR.
That is not representative of CMake in general. If there is a better
way for FindJNI to get the information it
On 02/10/2016 09:30 AM, Thibault Genessay wrote:
>> While CMakeForceCompiler is deprecated we think it should still work
>> in most cases where it worked before, just with a warning. What
>> actually breaks?
>
> I downloaded 3.5 this morning and tried again. I get all the warnings,
> but the
On 02/10/2016 03:49 AM, Vania Joloboff wrote:
> We have not yet moved to 3.5 but seeing this discussion, I am wondering
> what we will have to do. In our project, we have several C and C++ cross
> compilers and we want to compare them on selected benchmarks. We also
> want to compare different
On 02/07/2016 01:54 PM, Michael Jackson wrote:
>> What is the oldest version of OS X that CMake actually runs on?
>> I guess I would support the last version of Xcode that actually
>> ran on that platform. In reality this is probably 10.6.8?
[snip]
On 02/08/2016 10:21 AM, Sean McBride wrote:
>
On 02/07/2016 01:54 PM, Michael Jackson wrote:
>> What is the oldest version of OS X that CMake actually runs on?
>> I guess I would support the last version of Xcode that actually
>> ran on that platform. In reality this is probably 10.6.8?
[snip]
On 02/08/2016 10:21 AM, Sean McBride wrote:
>
Hi Thibault,
Thanks for trying the release candidate!
On 02/09/2016 09:10 AM, Thibault Genessay wrote:
> I installed 3.5 and the build broke
While CMakeForceCompiler is deprecated we think it should still work
in most cases where it worked before, just with a warning. What
actually breaks?
>
On 02/04/2016 11:00 AM, Thompson, KT wrote:
> #6 cmInstallCommand::InitialPass (this=0x1417360, args=std::vector of length
> 5, capacity 5 = {...}) at .../cmake-3.5.0-rc1/Source/cmInstallCommand.cxx:103
> (at 0x0089ac4a)
> #5 cmInstallCommand::HandleExportMode (this=0x1417360,
On 02/04/2016 04:00 PM, Thompson, KT wrote:
> If I run ‘make VERBOSE=1’ with CMake-3.4.3, I see the following command:
>
> cmake -E cmake_copy_f90_mod src/dir1/dir2/myf90file
> src/dir1/dir2/CMakeFiles/Lib_FC_f90sub.dir/myf90file.mod.stamp Intel
>
> but with CMake-3.5.0-rc1, I have this command
On 01/28/2016 11:04 AM, Taylor Braun-Jones wrote:
> Is this expected behavior, a known bug, or a new bug that I should file?
Currently it is expected, but I don't think anyone has thoroughly
investigated it or tried to implement it. IIRC it works in Makefile
generators only because the make tool
On 02/03/2016 11:19 AM, Thompson, KT wrote:
> On RHEL 6.7, I extracted the prebuilt x86_64 binaries from the
> downloaded .tar.gz file. At the end of the configuration process,
> cmake issues a segmentation fault and no Makefiles are generated.
What project are you configuring?
Can you provide
On 02/03/2016 11:19 AM, Thompson, KT wrote:
> The Windows installation doesn’t appear to provide all the
> required dependencies. ‘cmake-gui’ will not launch and provides
> the error “Qt5Widgets.dll is missing form your computer.”
Ugh, after months of working correctly on the nightly binary
On 01/21/2016 07:53 AM, Gonzalo wrote:
> I delved into the cmake 3.4.2 source code and found the offending line
> in cmTarget.cxx:
>
> cmSystemTools::ExpandListArgument((*it)->ge->Evaluate(mf,
>config,
>
On 01/20/2016 04:36 PM, Andrew Maclean wrote:
> "CMake Error at CMakeLists.txt:1 (project):
> Could not find an appropriate version of the Windows 10 SDK installed on
> this machine"
>
> In CMakeOutput.log, there is one line:
> "The system is: Windows - 10.0.10586 - AMD64"
It looks like
On 01/21/2016 11:00 AM, Gonzalo wrote:
> Find attached the mrViewer/src/CMakeList.txt file that still fails.
Thanks. From that I was able to reproduce it in a small test case
with CMake 3.4. It appears that the problem has been fixed since
then in 'master'. I've added a test case to keep it
On 01/25/2016 04:12 PM, Gonzalo Garramuño wrote:
> Does this one have the fix for the FLTK_WRAP_UI?
No, sorry. 3.4.3 was released only as a quick fix to 3.4.2's problems
on Windows 10. 3.5 will have the fltk fix, and the freeze for that is
next week.
-Brad
--
Powered by www.kitware.com
On 01/19/2016 11:48 PM, Andrew Maclean wrote:
> Works well, although I did find that I had to update my Windows SDK
> to 10.0.10586.0 when using Visual Studio 2015 on Windows 10.
> This is because CMake detected the system as Windows - 10.0.10586 - AMD64.
> This was not the case with the previous
On 01/19/2016 08:42 PM, Gonzalo wrote:
> I compiled v3.4.2 and after installing it in /usr/local, I tried running
> it in a project that was working fine with cmake 2.8.
Thanks for reporting this. The 2.8 series was quite long. To help narrow
the changes between these versions, what 2.8
On 02/15/2016 12:47 PM, James Crosby wrote:
> Using a dummy link command to check that linking works seems to
> undermine the purpose of checking in the first place, which suggests
> that perhaps it should still be possible to skip the check?
For reference, this discussion has moved to the
On 03/12/2016 05:19 PM, Roman Wüger wrote:
> Yes, i use fixup_bundle.
> Is there a better alternative?
No, but you'll have to trace through its execution to see where it
picks up the dependency on wintrust.dll.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the
On 03/11/2016 02:41 AM, Roman Wüger wrote:
> i noticed that CPack includes the WINTRUST.dll when I
> generate an NSIS installer.
> How can I avoid this?
> I have no dependencies to this library.
CMake has no mention of that dll in its source so we are not adding
the dependency explicitly
On 04/06/2016 03:47 PM, Gregor Jasny wrote:
> On 06/04/16 20:32, Matthew Keeler wrote:
>> clang: error: no such file or directory:
>> '.../lib/example.build/Debug/example.build/Objects-normal/x86_64/x.o'
>>
>> Within the directory
>> .../lib/example.build/Debug/example.build/Objects-normal/x86_64
On 04/12/2016 02:54 PM, Robert Dailey wrote:
> set_target_properties( ALL_BUILD PROPERTIES FOLDER ${predefined_folder} )
>
> if( BUILD_TESTING )
> set_target_properties( RUN_TESTS PROPERTIES FOLDER "Testing" )
> endif()
>
> However this fails stating those targets do not exist.
They don't
1101 - 1200 of 15210 matches
Mail list logo
