Hi Brad,
adding set(CMAKE_INCLUDE_FLAG_C "-I ") (and, just to be sure, its C++
cousin) did the trick all right. I can now build PLplot's Fortran
bindings and examples using the Compaq Visual Fortran compiler.
The only thing that worries me is that this may have an impact on
the C compiler too, a
Hi Brad,
thanks for this detailed explanation. I will try again with these
amendments.
(I detest the introduction of spaces in directory names and file names.
It messes up all manner of things! Yes, you are right, quotes won't
solve the issue.)
Regards,
Arjen
On 2010-02-16 16:12, Brad King wr
Arjen Markus wrote:
> f90.exe /compile_only -IF:\plplot-svn\plplot\bindings\f77\strutils.f
>
> Compaq Visual Fortran has an option /include or /I or -I but also an
> option /iface:keyword or -IF:keyword.
>
> In this particular constellation it is interpreting the options in the
> wrong manner
Hi Brad,
I created a new issue in the CMake tracker regarding the refactoring
of the file Windows-Compaq-Fortran.cmake, as you wil have seen.
I tried some further tests today and was rather astonished to see
it all fail ... with a message from the Compaq compiler that it
was passed a keyword to
Hi Brad,
On 2010-02-02 13:38, Brad King wrote:
Arjen Markus wrote:
Hi Brad,
I just tested the patch - Compaq Visual Fortran is recognised,
but not accepted - and added the Windows-f90.cmake file from the
PLplot project to CMake's Modules\Platform directory. Now the
compiler is accepted as well
Arjen Markus wrote:
> Hi Brad,
>
> I just tested the patch - Compaq Visual Fortran is recognised,
> but not accepted - and added the Windows-f90.cmake file from the
> PLplot project to CMake's Modules\Platform directory. Now the
> compiler is accepted as well.
The "Windows-f90.cmake" name is the
Hi Brad,
I just tested the patch - Compaq Visual Fortran is recognised,
but not accepted - and added the Windows-f90.cmake file from the
PLplot project to CMake's Modules\Platform directory. Now the
compiler is accepted as well.
Note: I just saw there is already a Windows-df.cmake file in the
re
Hi Brad,
great, I should have time tomorrow to report back.
Regards,
Arjen
On 2010-02-01 15:26, Brad King wrote:
Arjen Markus wrote:
On 2010-01-28 17:18, Brad King wrote:
Thanks. Undo the previous patch and try the one below instead.
I applied the patch and it all worked fine. That is, C
Arjen Markus wrote:
> On 2010-01-28 17:18, Brad King wrote:
>>
>> Thanks. Undo the previous patch and try the one below instead.
>>
>
> I applied the patch and it all worked fine. That is, CMake now
> recognises the compiler but does not test it with the correct
> compile flags (-o being reported
Hi Brad,
On 2010-01-28 17:18, Brad King wrote:
Thanks. Undo the previous patch and try the one below instead.
I applied the patch and it all worked fine. That is, CMake now
recognises the compiler but does not test it with the correct
compile flags (-o being reported as ambiguous). I can
Hi Brad,
I will try the new patch tomorrow.
I tried printing it as an ordinary variable or constant, but that did
not work: variable names are not allowed to start with an underscore.
Regards,
Arjen
On 2010-01-28 17:18, Brad King wrote:
Arjen Markus wrote:
Perhaps this means that _DF_VERSIO
Arjen Markus wrote:
>> Perhaps this means that _DF_VERSION_ is available only as a Fortran
>> language symbol.
>
> It would look that way, but what use would it have then?
Perhaps it can be used in regular (runtime) IF tests? Of course other
compilers won't define it, so it's useful only in vend
Hi Brad,
Perhaps this means that _DF_VERSION_ is available only as a Fortran
language symbol.
It would look that way, but what use would it have then?
So we conclude that the compiler provides no way to identify itself
using the preprocessor. This will need non-trivial work in CMake to
re
Arjen Markus wrote:
> the program is compiled and linked without a problem. But
> it writes:
> INFO:compiler[]
> INFO:platform[Windows]
>
> I have examined the preprocessed source code and re-read the
> online documentation: all the macros defined in the table I
> looked at are available to the pr
Hi Brad,
the program is compiled and linked without a problem. But
it writes:
INFO:compiler[]
INFO:platform[Windows]
I have examined the preprocessed source code and re-read the
online documentation: all the macros defined in the table I
looked at are available to the preprocessor, except, indee
Arjen Markus wrote:
> it does not work - I get a message that the Fortran compiler
> identification is unknown. Does CMake run the compiler with the
> /fpp option? If not, then that is the cause (without there is
> no particular macro defined)
In CMakeDetermineFortranCompiler.cmake we list the pos
Hi Brad,
it does not work - I get a message that the Fortran compiler
identification is unknown. Does CMake run the compiler with the
/fpp option? If not, then that is the cause (without there is
no particular macro defined)
Regards,
Arjen
On 2010-01-28 14:27, Brad King wrote:
Arjen Markus wr
Arjen Markus wrote:
> If you turn on the preprocessor option, then a number of macros
> are defined, the most useful being:
>
> _DF_VERSION_=660 and _VF_VERSION_==660
Please try out the patch below (applies to CMake from CVS HEAD).
With it, CMake should recognize the Compaq compiler out of the bo
Hi Brad,
see my answers below
On 2010-01-27 19:18, Brad King wrote:
Brad King wrote:
As a first step, we can add Compaq to CMakeFortranCompilerId.F.in.
What is the preprocessor macro that identifies it?
I'd like to teach CMake upstream to recognize the Compaq Fortran
compiler even if we do n
Brad King wrote:
> As a first step, we can add Compaq to CMakeFortranCompilerId.F.in.
> What is the preprocessor macro that identifies it?
I'd like to teach CMake upstream to recognize the Compaq Fortran
compiler even if we do not provide platform files for it yet.
CMake already recognizes the Com
You can always just set the environment variables:
FC == path to comiler
FFLAGS == options for the compiler
Then run cmake on a clean build tree, and it should use those values.
-Bill
At 06:13 AM 8/31/2006, Arjen Markus wrote:
>Hello,
>
>some further information on Fortran compilers:
>I have
Hello,
some further information on Fortran compilers:
I have added g95 as a compiler to the list in
CMakeDetermineFortranCompiler.cmake and it simply worked.
Quite possibly the various compiler options need more tuning,
but it is a start :).
Regards,
Arjen
Hello,
I am trying to modify a module that will properly recognise Compaq Visual
Fortran on Windows and set all relevant properties. The problem I
encounter isthat the OBJECT variable as used in the CMAKE_xxx_COMPILE variables
does not contain the native path to the object file, whereas the TARGET
23 matches
Mail list logo
