View previous topic :: View next topic |
Author |
Message |
JugoslavDujic
Joined: 10 Nov 2005 Posts: 7
|
Posted: Mon Nov 14, 2005 9:24 am Post subject: Location of .OBJ and .MOD Files (porting woe #4) |
|
|
I'm porting my [url="http://www.xeffort.com/xeffort/home.htm"]Xeffort GUI library[/url] from Visual Fortran to FTN95 (among other compilers). The code uses a lot of "smart" non-standard tricks (since VF has pretty much full capabilites of C language) and I'm trying to find out how to find equivalent constructs in FTN95.
The structure of local directories in the solution are complicated enough; I have it pretty tidied up. The idea is that Package directory contains only source files and files that should be ultimatively distributed (.LIB and .MOD). However, I can't find any setting for FTN95 to tell where I want .obj files, where I want .lib file and where I want .mod file. I'd like to have the following structure:
[pre]
/Package
+--/IncludeFTN (.MOD files)
+--/LibFTN (.Lib files)
+--/Source (.f90 files)
+--/Xeffort_FTN (.ftn95p file)
+--/Temp
+--/ReleaseFTN (.obj files)
[/pre]
However, the compiler insists to put the .obj and .lib file to /Package/Xeffort_FTN/Release/Win32 and .MOD files into /Package/Xeffort_FTN directory (despite the fact that I set up "Module path" and "Include path" to ../IncludeFtn, trying both relative and absolute path).
Is there some setting I'm missing? I feel this feature is so simple that it should be included in compiler, but then... (and I don't feel like specifying .obj file for every source file separately using the option... /NAME or like?)
--
Jugoslav _________________ %2D%2D%0D%0AJugoslav |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7931 Location: Salford, UK
|
Posted: Tue Nov 15, 2005 12:55 am Post subject: Location of .OBJ and .MOD Files (porting woe #4) |
|
|
Jugoslav
We need to distinguish between what the compiler is doing and how Plato uses the compiler.
If you want full control of the compiler then you should use a Command Prompt window and then use FTN95 commands as described in the help file.
From the command line you can set the path for reading mod files etc as you say. I think that you will find that mod files are always written to the same folder as the source (but I would need to check this in the help file). OBJ files can be written to a given folder by using the /BINARY switch.
Once you have understood what happens on a raw command line, you can aim to set the Plato Project Properties to get the same effect. You should be able to change the output folder in this way but I am not sure that you can change the folder to which the mod files are written. |
|
Back to top |
|
|
|