Hello,
Thank you for your replies (Rob and Eric).
I changed my PATH to put my LIBS in c:\MyCode\LIBS and
my includes in c:\MyCode\INCS:
use Inline C => Config => INC => '-I c:/myCode/INCS';
use Inline C => Config => LIBS => '-L c:/myCode/LIBS
-lolimg32';
use Inline C => Config => BUILD_NOISY => 1;
use Inline C => <<'END_OF_C_CODE';
#include <olwintyp.h>
extern OlImgOpenDevice(char *);
void greet (char *) {
printf("HELLO");
olImgOpenDevice("FFF");
}
END_OF_C_CODE
greet(42);
What I meant to say in my earlier email (I was not
clear) is that when I get my undefined reference to
OlImgOpenDevice, I cannot see my -L or -l options
passed into the compiler anywhere on the screen.
One other interesting note:
When I put ONLY this at the top of my source file for
"use Inline C => CONFIG" options:
use Inline C => Config => INC => '-I C:/MyCode/INCS';
then I see "-I C:/MyCode/INCS" passed to cl.exe but
when I put any other Config options after it (like
LIBS or BUILD_NOISY) then the "-I C:/MyCode/INCS" does
not show up on my list of parameters to cl.exe and I
get "Cannot open include file "olwintyp.h". It is like
my Config => INC is getting wiped out by future calls
to "use Inline C => Config"
Also, thanks for the BUILD_NOISY option but
unfortunately that did not show my any additional
warnings.
Eric, even though it did not seem like a file path
problem I went ahead and installed Inline-0.44_01 (by
doing a perl Makefile.pl) from the directory where
Inline-0.44_01 was extracted.
I seem to be the only one having this problem. I know
I will get his working with your help.
Thanks,
Todd
--- Sisyphus <[EMAIL PROTECTED]> wrote:
> >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
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
