On Tue, May 14, 2013 at 03:55:37PM -0400, Bill Hoffman wrote:
Globs simply do not work well for source files.
GLOBs work great for source files. Just not with CMake currently ;]
I don't think this will be come a module in CMake.
To have this work in a generic way, you would have to run
On 5/15/2013 4:48 AM, Wojciech Knapik wrote:
On Tue, May 14, 2013 at 03:55:37PM -0400, Bill Hoffman wrote:
Globs simply do not work well for source files.
GLOBs work great for source files. Just not with CMake currently ;]
No it does not. It is sloppy IMO. It will pick up junk files.
On 05/14/2013 05:42 PM, Robert Dailey wrote:
What target property does TARGET_FILE_DIR access when used in a
generator expression? I'm thinking I might be able to set the output
directory directly to the custom target for each configuration. If I
know which target property to set, this might
On Wednesday 15 May 2013, Bill Hoffman wrote:
On 5/15/2013 4:48 AM, Wojciech Knapik wrote:
On Tue, May 14, 2013 at 03:55:37PM -0400, Bill Hoffman wrote:
Globs simply do not work well for source files.
GLOBs work great for source files. Just not with CMake currently ;]
No it does not.
On 05/13/2013 05:15 PM, Kamil Rytarowski wrote:
There is an old known problem with the NCurses library: missing links
against ncursesw, and additionally ncursest with ncurseswt [1].
There is a bug report [2] marked as a backlog
I've cross-linked that issue back to this thread:
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14143
==
Reported By:vitaut
Assigned To:
On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote:
I’m pleased to announce the first release candidate of CMake Tools for
Visual Studio, an extension adding support for syntax highlighting and
IntelliSense in CMake code using Microsoft Visual Studio. The extension is
open
Yup; painless to install, works as described :) Thanx
On Wed, May 15, 2013 at 4:37 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote:
On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote:
I’m pleased to announce the first release candidate of CMake Tools for
Visual Studio,
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=14145
==
Reported By:Ho Cheung
Assigned To:
Den 13. mai 2013 20:08, skrev Pritchett-Sheats, Lori:
Each dir* has *.F files that must be preprocessed to *.f90 files and
then compiled.
Hi,
Just to give my two cents here. The standard filenaming scheme for
fortran files are unless otherwise specified in the
compile/preprocessing flags (as
File in which error comes are , archieve_read_disk_posix.c
archieve_write_disk_posix.c :--
These files have following include file :---
#ifdef HAVE_FCNTL_H
#include fcntl.h
#endif
Now if we see the dependencies :---
/usr/include/fcntl.h -contains file --- # include
Thank you! That fixed it.
And yes, I had a typo. should have been F90Library_SOURCE_FILES.
Lori A. Pritchett-Sheats
Los Alamos National Laboratory
CCS-2, Computational Physics
505-665-6675
From: Brad King [brad.k...@kitware.com]
Sent: Tuesday, May
Yes the files are not following the file extension standards. This is a legacy
project from the late 1990s, early 2000s.
I did change the file extensions to *.F90 to work around my current problem to
move forward with other tasks and I discovered that while ifort pre-processed
files the code
Thanks for the response Andreas. For those poor souls who come after,
the solution is to do the following:
set(CMAKE_C_FLAGS -mmcu=msp430fr5739 -D__MSP430FR5739__
-ffunction-sections -fdata-sections -DGCC_MSP430 -Wall -g -std=c99
CACHE STRING FORCE)
Using the FORCE attribute forces the
On Thu, Sep 22, 2011 at 12:25 AM, Lukas Anzinger l.anzin...@gmail.comwrote:
Hi,
I'm aware of the option CMAKE_BUILD_TYPE with which I can tell if I
want to include debugging information or not.
A very useful feature of the program objcopy is, to not strip
debugging information from a file
I have a fortran code that I'm compiling twice to generate two libraries. There
is a USE statement inside a preprocessor conditional. It looks like cmake is
not picking up the dependency because of it. The code in question is
SUBROUTINE calc_fbal(bsubu, bsubv)
...
USE
On 05/15/2013 04:10 PM, Mark Cianciosa wrote:
I have a fortran code that I'm compiling twice to generate two libraries.
There is a USE statement inside a preprocessor conditional. It looks like
cmake is not picking up the dependency because of it. The code in question is
SUBROUTINE
On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote:
I’m pleased to announce the first release candidate of CMake Tools for
Visual Studio, an extension adding support for syntax highlighting and
IntelliSense in CMake code using Microsoft Visual Studio. The extension is
open
I'm new to cmake, a few weeks ago I decided to convert a complex and decrepit
old build system to cmake. It has gone very well, I'm quite impressed.
So, now I want to add testing support, but I haven't been able to figure out a
few things.
1. What to do with testing input files? I wrote
Yup; painless to install, works as described :) Thanx
On Wed, May 15, 2013 at 4:37 PM, Klaim - Joël Lamotte mjkl...@gmail.com wrote:
On Wed, May 15, 2013 at 1:04 AM, David Golub golu...@gmail.com wrote:
I’m pleased to announce the first release candidate of CMake Tools for
Visual Studio,
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 b11ed88a3f11d0e6d1325f44a8bfdbf67e3b83a9 (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 925eb83c383e5734ced262c3df8ba3b31b80ff53 (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 143def6e9a77c4854e19870b513e0f473b514647 (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 bfc9deae93a58e82ceb92706b1428a7f85fd1165 (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 0ad0c37206fce114c4e4c31f5270b53e181ab3c2 (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 06f8701788cffce1d8abc5013a8b7483e2c2367f (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 4527d76a7f0ab32810e6cf0ff0143d37a8044804 (commit)
via
27 matches
Mail list logo
