Software Archive
Read-only legacy content
17060 Discussions

command line vs msdev

rahzan
New Contributor I
931 Views
produce a DLL w/ a single f90 file which contains a single module in it using:
1. msdev
2. command line: DF /dll filename.f90

There are no USEs or dependecy on other modules or libraries than the default.

compare the resulting LIB or DLL files using FC.
They are not identical....What gives?

Tim
0 Kudos
5 Replies
Steven_L_Intel1
Employee
931 Views
Compare the compiler and linker options under MSDEV to those you're using on the command line. They won't be the same. In particular, the Developer Studio project will use /libs:dll

Steve
0 Kudos
rahzan
New Contributor I
931 Views
I tried looking these things up but the only htings I see are /pdb and./implib and these are set tothe default name.pdb and name.lib
I did not see /libs:dll where would I find this?

Thanks, Tim
0 Kudos
Steven_L_Intel1
Employee
931 Views
Sounds to me as if you're looking at the link options, not the Fortran options.

Steve
0 Kudos
rahzan
New Contributor I
931 Views
Well I looked there before I wrote. Nothing worthy of note and esp no /libs. Here is what is under fortran tab:

/compile_only /dll /nologo /warn:nofileopt /module:"Release/" /object:"Release/"

Further ideas will be appreciated
Tim
0 Kudos
Steven_L_Intel1
Employee
931 Views
Well, since you didn't say what was different about the DLLs, I just took a guess. There's nothing magic about the DevStudio interface - it just invokes the command-line compiler behind the scenes. If you manually add /watch to the Fortran project options box and do a build, you'll see in the build window the exact commands used. Perhaps that will help you.

Steve
0 Kudos
Reply