location of library files

[Brian_Allison]

I was wondering if there is a compiler option to tell the compiler where to look for the library files.

Here is what I have in my makefile.

$(f90) -nologo $(FFLAGS) $(FPSTOP) $(FL) \\

-thread -dbglibs relap\\relap5.$O -libs:qwin \\

relap\\relap$(NM).lib scdap\\scdap$(NM).lib \\

matpro\\matpro$(NM).lib relap5l.lib \\

envrl\\envrl$(NM).lib graphics\\graphics.lib -libs:qwin\\

libifcoremt.lib libifport.lib \\

libmmt.lib kernel32.lib ifqwin.lib gdi32.lib \\

user32.lib libirc.lib comdlg32.lib ifqw_mdi.lib \\

libcmt.lib imagehlp.lib opengl32.lib graphics\\glaux.lib \\

graphics\\glu32.lib \\

graphics\\libi\\f90gl.lib graphics\\libi\\f90glu.lib \\

graphics\\libi\\f90glut.lib graphics\\libi\\glut32.lib \\

-exe:bin\\relap5$(NM).exe -link \\

-heap:1000000000 -stack:14000000 -incremental:no -nodefaultlib

Instead of listing each library file. I have put them all into one folder. Can I just tell it to look to the special folder?

[Brian_Allison]

I have never used "-nolibdir". Yes I re-compiled all source.

Here is the dump bin.

[bash]Microsoft  COFF/PE Dumper Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.


Dump of file relapaccum.o

File Type: COFF OBJECT

   Linker Directives
   -----------------
   -defaultlib:"ifconsol"
   -defaultlib:"libifcoremt"
   -defaultlib:"libifport"
   -defaultlib:"libmmt"
   -defaultlib:"LIBCMT"
   -defaultlib:"libirc"
   -defaultlib:"svml_dispmt"
   -defaultlib:"OLDNAMES"

  Summary

         CC0 .data
          B9 .drectve
         3D0 .rdata
        2980 .text
         480 .trace[/bash]

[Steven_L_Intel1]

And did you rebuild the .lib?

[Brian_Allison]

I did a clean and started from a fresh source. All libs were rebuilt.

[Steven_L_Intel1]

Well, the symptom is that either the libraries you're linking to were compiled with -nolibdir or the linker option to disable library directives was added. The output from the dumpbin also tells me that source was not compiled with -libs:qwin.

Is this in fact a QuickWin application and are there QuickWin calls from one of the DLLs you're using? That won't work.