>I have been trying forever (and am running out of > time) to use: > use Inline C => Config => LIBS => > > and I use a symbol that is in the library that I > specify in LIBS but when I compile my program I get an > error that my symbol is undefined and I look at the > compiler output and dont see it ever putting my -L or > -l in the compile options hen I look at the output of > the compiler options.
How does one "look at the output of the compiler options" ? (If someone tells me, I will compare what I get against what Todd found and verify that the -L options ought to, in fact, show up on Win32.) > I am using Visual C++ 6.0 an the > cl.exe compiler. I have tried everything > that I could think of but can get my LIBS directory or > LIBS library to show up on my comple options. INC > seems to show up in my compile options but not LIBS. > Have you ever seen this problem? I think it's good advice to avoid directories with spaces. However, in this case, it looks to me that what you did should work (assuming that the paths are valid) - at least the use of double quotes like that works for me on Win32. I would try adding the Config option BUILD_NOISY=>1 and look for any warnings that get issued especially one like: Note (probably harmless): No library found for -lolimg32 which in this case would definitely *not* be harmless. If no such warning is issued then we can safely say that the library was found and the undefinition results from something else. Cheers, Rob
