I'm porting my Xeffort GUI library 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