forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

FTN95 configuration dialog

 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support
View previous topic :: View next topic  
Author Message
LitusSaxonicum



Joined: 23 Aug 2005
Posts: 1598
Location: Yateley, Hants, UK

PostPosted: Wed Jun 21, 2017 9:03 pm    Post subject: FTN95 configuration dialog Reply with quote

What makes FTN95 bring up the configuration dialog when given a command line such as:

ftn95 /c test.for

And as the only way out of that dialog is Save and the exit box, then it does not do the compilation?

8.10pe (and others)

Eddie
Back to top
View user's profile Send private message
JohnCampbell



Joined: 16 Feb 2006
Posts: 1723
Location: Sydney

PostPosted: Thu Jun 22, 2017 12:57 am    Post subject: Reply with quote

Eddie,

This function of /c option came up in a recent post, as it now initiates the /cfg option. ( /config for local .cfg file )
I am not sure if "/c" has always been the abbreviation for /cfg or if a recent change to FTN95. I think /cfg may be new ?

This becomes a problem for users not familiar with FTN95, as /c is a necessary option for gFortran and ifort when producing .obj files.

Perhaps FTN95 could be changed so that /c is not an abbreviation for /cfg or /config. ( /config_local might be better for local or provided in File options)
It may be better if /c could possibly be reported as an invalid option for FTN95 or made to act as with most other compilers, ie select that .obj file is produced and /lgo or /link are not compatible options.

The short answer is that you have selected incompatible options so user error !

John

update: /c (/cfg) was introduced with Ver 8.00. Prior to this /c implied /cfpp which may have caused less conflict.

Could I suggest that options /c and /32 be considered as new options to be used to help with documenting the compile command, which would be used by FTN95 to confirm the compatibility of compile options being selected.
Back to top
View user's profile Send private message
PaulLaidler
Site Admin


Joined: 21 Feb 2005
Posts: 4776
Location: Salford, UK

PostPosted: Thu Jun 22, 2017 8:56 am    Post subject: Reply with quote

John is right. Compiler command line options can be abbreviated and the result is based on lexicographic order. So the effect of /c has changed with the introduction of /cfg.

For gFortran, use -c to generate code.
For FTN95, use /no_code to avoid generating code.

I guess that (in FTN95) /c could be added as an alternative to /-no_code but it might cause confusion particularly when used in a configuration file.
Back to top
View user's profile Send private message
LitusSaxonicum



Joined: 23 Aug 2005
Posts: 1598
Location: Yateley, Hants, UK

PostPosted: Thu Jun 22, 2017 9:40 am    Post subject: Reply with quote

Thanks both,

I've been using /c for well over a quarter century to just compile and produce an .obj - perhaps it never did anything at all!

Eddie
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group