On 08/01/2014 02:22 PM, Chuck Atkins wrote:
I noticed the recent merge of liblzma broke the PGI compiler.
It is not surprising that there is lingering C99 code because
the library implementation was ported from C99 to C89/90 for
inclusion in CMake.
+#if defined(__STDC_VERSION__)
On 08/04/2014 09:57 AM, Chuck Atkins wrote:
Given that it was ported though, I'd say the better fix would be
to remove the C99 version entirely and always use the C89 version
without the static array dimensions. See updated patch.
Agreed, but that looks like the same patch again.
-Brad
--
+#if defined(__STDC_VERSION__) (__STDC_VERSION__ 199901L) \
Did you mean = 199901L here rather than ?
I did, that was a typo.
On 08/01/2014 02:22 PM, Chuck Atkins wrote:
I noticed the recent merge of liblzma broke the PGI compiler.
It is not surprising that there is lingering C99
Will this Tegra work become a generic Android generator? Or is it Tegra
specific (it looks like a modification of the Visual Studio generators)?
Cheers,
Tim
Date: Wed, 09 Jul 2014 10:02:48 -0400
From: Brad King brad.k...@kitware.com
To: cmake-developers@cmake.org
Subject: Re:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=15058
==
Reported By:Nate Eldredge
Assigned To:
Hi,
I'm trying to use cmake in my project. In fact, it is my first time using
cmake.
My CmakeList file is below. You can see it is very simple because I'm
trying to compile a binary.
cmake_minimum_required(VERSION 2.8)
project(2pg_cartesian)
set(PROJECT_VERSION 1.0)
Hi Rodrigo,
Where is the implementation of the undefined references?
If it is in another source file (other than protpred-Gromacs-NSGA2.c, which
seems to be the only one you are compiling) you should add it to the
compilation. If it is in another library that is already compiled, you
should add
Hi Rodrigo,
It looks like you are probably missing some source files in your
executable. Is protpred-Gromacs-NSGA2.c the only piece of code that gets
built for the executable? If not, you'll need to make sure that all the
necessary source files get either built into the executable or build as a
Thanks Chuck and Angeliki. Thanks your help.
However, unfortunatelly, I couldn't fix.
In [1] I show all my project. In src directory there is all .c files. In
include directory there is .h files.
The protpred-Gromacs-NSGA2.c is one of executable. The others are:
protpred-Gromacs-Dominance.c,
Hi Rodrigo,
You have to state to cmake all of your source files for compilation,
otherwise they won't be found in the generated makefiles.
You can do this either by writing all file names individually in
add_executable, or create a variable or a list that contains all of the
file names, or
On 8/4/2014 10:26 AM, Rodrigo Faccioli wrote:
protpred-Gromacs-NSGA2.c:(.text+0x1e): undefined reference to `display_msg'
protpred-Gromacs-NSGA2.c:(.text+0x3e): undefined reference to
`load_parameters_from_file'
protpred-Gromacs-NSGA2.c:(.text+0x58): undefined reference to `ea_nsga2'
I converted a project from autotools/handmade makefiles to cmake and
afterwards I added NSIS packaging for win32 builds via the cpack
integration.
Everything was fine while the version patch level was being used, but upon
the next release 0.97 w/o a patch level the resultant installer has the
Hi Chuck,
seems a bit hackish, but works for me :)
Thanks for the trick!
nick
On Fri, Aug 1, 2014 at 12:37 PM, Chuck Atkins chuck.atk...@kitware.com wrote:
Hi Nick,
You could split your target in to two object libraries that combine into a
singe real library:
add_library(foo_f OBJECT
Hi Chuck,
I am building both static and shared libraries using the object files.
After splitting the Fortran and C source as you suggest, I get the
following linker error:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld:
The solution is to add the POSITION_INDENPENDENT_CODE target property
to the C and Fortran convenience library targets.
Thanks again for the help,
nick
On Mon, Aug 4, 2014 at 3:35 PM, Nicolas Bock nicolasb...@gmail.com wrote:
Hi Chuck,
I am building both static and shared libraries using the
I've been trying to figure out how to correctly author install steps for
a library that will generate a self-contained folder that can be
distributed and used by others, including a good packageConfig.cmake
file and I ran into what seems like a bug. If you say
install(EXPORT package
Glenn, thanks for the tip. Those two options are new to me.
It's not very clear to me how the add_compile_options function works.
Complexity might be added when I mention that I've also defined 4 new
custom languages (all essentially identical to C). When
add_compile_options is executed, will
Poking around some more I think I may have found a better solution.
# Toolchain file
include(FileWithInitFlags.cmake)
set(CMAKE_C_COMPILE_OBJECT
CMAKE_C_COMPILER DEFINES FLAGS ${CMAKE_C_FLAGS_INIT} -o
OBJECT -c SOURCE)
And for the custom languages I can add that to
Hi,
I'm wondering what is the best way to do feature detection or version
checking of cmake itself, in cmake. In particular, I'd like to check for
the OBJECT library feature and either use it or fall back to our current
mechanism if we're using an older cmake.
--
Cheers,
Leif
--
Powered by
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via d6c600ce367dac81b82da04bd17abbbfc726df36 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 8d53830cef29277af80ebdf666349e386f22e0c9 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via ed9d665de5d2c949b607e1669ce59a985b9b3f8a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 506ed92c68ebc5494bd65d9c10eb8123a3bd3321 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 1a1f6526f308d87a22071539acda3a6da49d9e82 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via eb2eb7840ae2706aadeb9e8015656ed03843acd1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0bb1daddaf0f450b8d040015c9135ad85fee9378 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via af5b8256b4d3ca1b65f5f97424918e241e360213 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 4c83a4e74d4e13307504ff681269776ef0878246 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0df50f497c4c4937e882b6ea7048980e52e855d0 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 2ce89b454085b5432bdf05f0c86af0e3879f6c75 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 7b81cf8943c519fa76c781afdcdc54eac08b3bfb (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 6562e3204db04bf6f5256b090db751d0ca9136dd (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via f1971971c9c23f1d2819d64e189ce01a15362ac4 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via e951857e6a54a6920e4ab9d198c4d6a4612285bd (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via e9a89912e887da393c818d0fc2a84c6798fcfe2e (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via aa373eb723dc596e8b129a6b2f279df27f6d3dda (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 0c47c2f90796aab40911b3595870801bae6ba7d7 (commit)
via
20140804)
+set(CMake_VERSION_PATCH 20140805)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
38 matches
Mail list logo