While the cmake man page does not document the proper capitalization of
Fortran for creating a fortran based project, I am now at the point the
compilation does not work for another reason.
Does anyone have an idea what this means?
Clearing dependencies in "CMakeFiles/pisces.dir/depend.make".
Cl
On 2007-09-25 22:37-0500 John Doe wrote:
While the cmake man page does not document the proper capitalization of
Fortran for creating a fortran based project, I am now at the point the
compilation does not work for another reason.
Does anyone have an idea what this means?
Clearing dependencie
On Wednesday 26 September 2007 04:37:33 [EMAIL PROTECTED] wrote:
> While the cmake man page does not document the proper capitalization of
> Fortran for creating a fortran based project, I am now at the point the
> compilation does not work for another reason.
>
> Does anyone have an idea what this
It turns out that any word of the word Use or use as a word anywhere in
a comment causes the dependency scanner to use the next token on the
line as a module dependency.
So I changed all the code to use xUse and xuse.
Thanks,
Juan
Alin M Elena wrote:
> On Wednesday 26 September 2007 04:37:33 [E
Hi Bill,
I wouldn't mind taking a stab at it.
It would be easy enough to tell lex to drop any line starting with a
comment character. Something along the lines of:
^[cC].* {}
There seems to be a line in the lexer that does this, but it doesn't
appear that that the start condition, fixed_fmt, i
Juan Sanchez wrote:
It turns out that any word of the word Use or use as a word anywhere in
a comment causes the dependency scanner to use the next token on the
line as a module dependency.
So I changed all the code to use xUse and xuse.
The problem is well known, and much talked about.
The
Juan Sanchez wrote:
Hi Bill,
I wouldn't mind taking a stab at it.
It would be easy enough to tell lex to drop any line starting with a
comment character. Something along the lines of:
^[cC].* {}
There seems to be a line in the lexer that does this, but it doesn't
appear that that the start c
Anyone know what are the valid comment lines in all the Fortran variants?
I know of lines beginning with c, C, or * in the first column.
Juan
Bill Hoffman wrote:
> Juan Sanchez wrote:
>> Hi Bill,
>>
>> I wouldn't mind taking a stab at it.
>>
>> It would be easy enough to tell lex to drop any lin
Am Mittwoch, 26. September 2007 17:34:38 schrieb Bill Hoffman:
>
> A lex/yacc guru would be best to help out here. Basically we want
> the fortran parser to ignore all comment lines. I gave it a try a while
> ago, but did not get it to work. I suppose a hack solution would be to
> pre-process
Maik Beckmann wrote:
Am Mittwoch, 26. September 2007 17:34:38 schrieb Bill Hoffman:
A lex/yacc guru would be best to help out here. Basically we want
the fortran parser to ignore all comment lines. I gave it a try a while
ago, but did not get it to work. I suppose a hack solution would b
Juan Sanchez wrote:
Anyone know what are the valid comment lines in all the Fortran variants?
I know of lines beginning with c, C, or * in the first column.
Those are valid only in the fixed-form type of source code.
The exclamation mark (!) is valid in both free-form and fixed-form code
I'm converting a Fortran package that was using GNU make to build to CMake, but
I've run into a problem compiling F90 module code where the source code is
stored under many directories.
The package has a directory structure
src/
src/dir1
src/dir2
:
:
Each dir* has *.F f
Hello,
I am trying to compile my program using this CMake script:
https://pastebin.com/zgJhbFhj
with ifort or gfortran my script works fine, but with IBMs XL Fortran I
get an error:
> make
-- A library with BLAS API found.
-- A library with LAPACK API found.
-- MKLROOT:
-- IBM
-- DEBUG Flag -
Hi,
On Mon, May 13, 2013 at 09:31:46PM -0400, cmake-requ...@cmake.org wrote:
> I'm converting a Fortran package that was using GNU make to build to CMake,
> but I've run into a problem compiling F90 module code where the source code
> is stored under many directories.
>
> The package has a dire
Lori A. Pritchett-Sheats
Los Alamos National Laboratory
CCS-2, Computational Physics
505-665-6675
From: Andreas Mohr [a...@lisas.de]
Sent: Tuesday, May 14, 2013 1:14 AM
To: cmake@cmake.org
Cc: Pritchett-Sheats, Lori
Subject: Re: Compiling Fortran Modules A
Hi,
[disclaimer: quoting below is non-standard]
On Tue, May 14, 2013 at 10:48:22AM -0400, cmake-requ...@cmake.org wrote:
> Date: Tue, 14 May 2013 14:36:18 +
> From: "Pritchett-Sheats, Lori"
| Hmm. Files with directory specification.
|
| But then...
>
> > set(F90Library_SOURCE_FILES)
> > f
On 05/13/2013 02:08 PM, Pritchett-Sheats, Lori wrote:
> IMPLICIT_DEPENDS Fortran "${F_file}"
The custom command is running a C preprocessor, not a Fortran compiler,
so use "IMPLICIT_DEPENDS C".
> list(APPEND PGSLibIface_SOURCE_FILES ${new_file_f90})
Do you mean to append to F90Library_S
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
, 2013 3:13 PM
To: Pritchett-Sheats, Lori
Cc: cmake@cmake.org
Subject: Re: [CMake] Compiling Fortran Modules And
On 05/13/2013 02:08 PM, Pritchett-Sheats, Lori wrote:
> IMPLICIT_DEPENDS Fortran "${F_file}"
The custom command is running a C preprocessor, not a Fortran com
org
Subject: Re: [CMake] Compiling Fortran Modules And
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 unles
I found that by setting:
set(CMAKE_EXE_LINKER_FLAGS "-qmkshrobj")
I can include this fix for older verison.
set(CMAKE_SHARED_LIBRARY_CREATE_Fortran_FLAGS "-qmkshrobj")
Didn't actually have any effect on the linker flags.
Kind regards
Matthias Redies
On 07.06.2017 17:02, Matthias Redi
On 6/8/2017 5:13 AM, Matthias Redies wrote:
I believe my Error was discussed in:
http://public.kitware.com/pipermail/cmake/2015-January/059522.html
and solved here:
http://public.kitware.com/pipermail/cmake/2015-January/059547.html
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4729547a
22 matches
Mail list logo
