On Mon, Nov 2, 2009 at 2:30 PM, Brad King wrote:
>
> Unfortunately it looks like -Tf implies -fixed too so it does not
> work with free-format sources unless -free is also added. We cannot
> add -free automatically because some sources might be fixed. The
> solution ties into another item on my
That works for me. Thanks Bill!
On Fri, Oct 30, 2009 at 6:08 PM, Bill Hoffman wrote:
> Kelly (KT) Thompson wrote:
>
>> Hi,
>>
>> I am trying to use Intel ifort on Linux to compile source code that uses
>> the extension .F95. By default, ifort will not compile fil
Hi,
I am trying to use Intel ifort on Linux to compile source code that uses the
extension .F95. By default, ifort will not compile files with this
extension. To allow the compilation, the name of the source file must be
preceded by -Tf (treat the next option as fortran source). While I know how
ple if someone want see it.
> >
> > Bill, create I bug report o not?, with the first example.
> > With 2.8 rc3 don't work in windows (don't compile test file).
> >
> > Thanks.
> >
> > Sebastian
> >
> > On Fri, Oct 9, 2009 at 7:05 PM
have to use "TARGET_LINK_LIBRARIES( FortranProgram CLibrary
>> > stdc++ )" for link. Why?
>> > I attach second example if someone want see it.
>> >
>> > Bill, create I bug report o not?, with the first example.
>> > With 2.8 rc3 don't w
On Fri, Oct 9, 2009 at 12:49 PM, Bill Hoffman wrote:
> Kelly (KT) Thompson wrote:
>
> On Fri, Oct 9, 2009 at 6:15 AM, Sebas > spas...@gmail.com>> wrote:
>>
>>I send a example where happen explained before ( I have similar
>>struct in my Program). I inc
On Fri, Sep 25, 2009 at 12:06 PM, Eric Noulard wrote:
2009/9/25 Kelly (KT) Thompson :
> > Hi,
> >
> > I am having intermittent trouble executing
> >
> > $ cmake -E copy_directory /full/path/to/large/directory /new/path
> >
> > Originally, the copy_dir
Hi,
I am having intermittent trouble executing
$ cmake -E copy_directory /full/path/to/large/directory /new/path
Originally, the copy_directory was failing deep in my build system
(add_custom_command), but the failure is repeatable from the command line
(exactly as shown above). The failure mes
library(flib ftest.f)
set_target_properties( flib PROPERTIES LINKER_LANGUAGE Fortran )
Thanks,
-kt
On Tue, Jun 2, 2009 at 5:32 PM, Kelly (KT) Thompson
wrote:
> Bill,
> Thanks for offering to look into this problem with Intel Visual Fortran
> integrated into Visual Studio. We are trying to patch
Bill,
Thanks for offering to look into this problem with Intel Visual Fortran
integrated into Visual Studio. We are trying to patch up our CMake files so
that we can build using the Visual Studio IDE (NMake Makefiles work fine)
and have run into this where Intel Visual Fortran 11.0 (full version,
Hi,
I have a simple Fortran CMake project that fails to build for "Release"
build types but works for "Debug." Can someone tell me what is wrong with
the following?
! file main.f90
program main
print *, "Hello"
end program main
# CMakeLists.txt
cmake_minimum_required( VERSION 2.6 FATAL_ERROR
Hi,
I am having trouble writing CMakeLists.txt for a Fortran (Intel Visual
Fortran 10) project that needs to use the link flags "/libs:dll
/threads" (alternate "/MD"). I am generating a "Visual Studio 8 2005"
project. I have reduced the problem to a "hello world" F90 code:
program main
print
On Fri, Apr 4, 2008 at 2:56 PM, Maik Beckmann
<[EMAIL PROTECTED]> wrote:
> I use the VS with the intel 9.0 fortran compiler, but with the NMake or the
> MinGW Makefile generator. Building and debugging works fine when using a
> C/C++ - Makefile project.
I can live with nmake, but I was hoping
I've spent the last few days trying to convince CMake to configure a
toy FORTRAN project without success. I'm hoping that someone on this
list can point me in the right direction. Here are the details:
System setup:
Windows XP
Microsoft Visual Studio 8 2005
Intel Visual Fortran 10.1.014
CMake 2.
14 matches
Mail list logo