building a project and creating a dynamik link library
in [Fortran]
|
From: halise on 19 Sep 2005 02:28 hi, i am using Digital Visual Fortran 6.0 , and i have a few questions: 1- when i want to build a project, it gives me an error like that Linking... LINK : fatal error LNK1104: cannot open file "dfor.lib" Error executing link.exe. to correct this, i go Projects Settings=>Link=>Category(Input)=>Additional Library Path: C:\Program Files\Microsoft Visual Studio\DF98\LIB i used not to do that before for building my projects, but now i have to do. is there a way to build my project without such a linking error by avoiding adding additonal library path? 2- While creating a dll (dynamik link library) in fortran develper studio, can i use common blocks, allocate(array(size)) intrinsic function and pointers for arrays in my fortran source code?
From: Jugoslav Dujic on 19 Sep 2005 07:25 halise wrote: | hi, | | i am using Digital Visual Fortran 6.0 , and i have a few questions: | | 1- when i want to build a project, it gives me an error like that | | Linking... | LINK : fatal error LNK1104: cannot open file "dfor.lib" | Error executing link.exe. | | to correct this, i go Projects | Settings=>Link=>Category(Input)=>Additional Library Path: C:\Program | Files\Microsoft Visual Studio\DF98\LIB | | i used not to do that before for building my projects, but now i have | to do. | | is there a way to build my project without such a linking error by | avoiding adding additonal library path? Your lib (and include?) path got screwed (by installing some other Visual Studio component?). However, you can fix it permanently by adding it in Tools/Options/Directories/Library Files. | 2- While creating a dll (dynamik link library) in fortran develper | studio, can i use common blocks, allocate(array(size)) intrinsic | function and pointers for arrays in my fortran source code? Yes. You can do almost everything from a Dll which you would do from an .exe, with only a few limitations (which I'd skip explaining here as it's unlikely you'll encounter them). -- Jugoslav ___________ www.xeffort.com Please reply to the newsgroup. You can find my real e-mail on my home page above.
From: halise on 20 Sep 2005 03:47 thanks a lot, you helped me very much. i solved my library path problem, but i cant yet solve another one which i had thought that it caused by that library path problem. i cant view the subroutines (entry points) in the resultant dll with the dependency walker component of visual fortran, which is a very useful tool to view what kind of components there are in a dynamik link library, while i used to have no problem with that before that library path problem. thanks, Halise
From: bv on 22 Sep 2005 00:22 halise wrote: > > i cant view the subroutines (entry points) in the resultant dll with > the dependency walker component of visual fortran, which is a very > useful tool to view what kind of components there are in a dynamik link > library, while i used to have no problem with that before that library > path problem. Check dll exports with "dumpbin" utility. If they differ from what you see in Dependency Walker you probably need to reinstall the compiler.
|
Pages: 1 Prev: calling lapack routine from C++ Next: Warning: Because of COMMON............... |