[TRNSYS-users] Intel Visual Fortran Compiler 9.0 and logical

[keilholz, werner]

There have been issues accessing open LUNs in DLLs, but so far I've only
seen it in mixed language programming (e.g., for types written in C++) - see
the topic 
 
https://www.cae.wisc.edu/pipermail/trnsys-users/2005/000695.html
<https://www.cae.wisc.edu/pipermail/trnsys-users/2005/000695.html> 
 
for a possible workaround based on special cards. Another (brute-force)
approach consists in just adding your type to the main TRNSYS Dll and
recompile that (TrnDll.dll). 
 
I wonder what your 'problems to integrate the Intel Fortran Compiler' are.
There is a trick that you have to apply after opening a FORTRAN project
(such as one created by the TRNSYS Simulation Studio) in the Microsoft
Developer Studio: the project shows up as "C++" per default, and the
environment insists on compiling everything with the C++ compiler, .f90
extension or not.... :-( 
 
You just have to right-click on its name, and choose 'convert to FORTRAN
project'. The icons then turns into a blue 'F'.
 
I have no clue why this is necessary, but it makes the project usable from
within the Developer Studio, using all the right options as set up by the
TRNSYS Studio, etc. 
 
 
Hope this helps, 
 
Werner
  _____  

De : trnsys-users-bounces at engr.wisc.edu
[mailto:trnsys-users-bounces at engr.wisc.edu] De la part de Gottwald Dieter
Envoyé : mercredi 29 mars 2006 15:36
À : trnsys-users at engr.wisc.edu
Objet : [TRNSYS-users] Intel Visual Fortran Compiler 9.0 and logical units
 
I am unable to access files that are attached via the external files tab in
the component. INQUIRE states that the logical unit is not opened. The added
"/libs:dll" option to the linker, as suggested in the programmer's guide,
did not change the situation at all.
 
I am using the Intel Visual Fortran Compiler 9.0 to compile the code and
since it cannot integrate itself into the MS Visual Studio 2005, I am using
a makefile to create the dll so I guess I will have to use different options
to make it work.
 
I use the compiler options "/O2 /DWIN32 /DNODEBUG /D_WINDOWS /D_USRDLL
/D_WINDLL /D_MBCS /c /nologo" and the linker options "/libs:dll /dll
/nologo". Other than the problem described above, my dlls do work. Most of
the options were copied from the options that are used for a c++-project.
 
What shall I do?
 
Regards, Dieter
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/trnsys-users-onebuilding.org/attachments/20060329/29f1c3b0/attachment-0001.htm>