Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Release 15.12, RC1 has arrived
dcorbit:
My default Watcom 64 bit Fortran compiler location:
c:\Watcom\binnt64\wfl386.exe
My default Watcom 64 bit C/C++ compiler location:
C:\WATCOM\binnt64\wcl386.exe
MortenMacFly:
--- Quote from: dcorbit on December 11, 2015, 03:05:53 am ---Run a batch file to set the environment for a given compiler.
--- End quote ---
You know that you can setup environment variables per personality and per project using the envvars plugin? I don't think such feature is needed because you can do so already.
darmar:
There are problems with parsing Gfortran v5.* compiler messages because in v5.* the format of some messages was a little bit changed. The patch attached solves this problem.
Another older problem is that -fopenmp option should be added to the compiler and to the linker when user selects "Enable the OpenMP extensions" compiler option. The patch solves this problem also.
MortenMacFly:
--- Quote from: darmar on December 12, 2015, 04:12:34 pm ---There are problems with parsing Gfortran v5.* compiler messages because in v5.* the format of some messages was a little bit changed. The patch attached solves this problem.
Another older problem is that -fopenmp option should be added to the compiler and to the linker when user selects "Enable the OpenMP extensions" compiler option. The patch solves this problem also.
--- End quote ---
I've applied this on trunk. Before I move it to the release branch: Is it backwards compatible? Meaning what happens to older GFortran compiler messages now?
darmar:
--- Quote from: MortenMacFly on December 13, 2015, 07:07:10 am ---Is it backwards compatible?
--- End quote ---
Yes, GFortran 4.* messages are recognized as before.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version