----- Original Message ----- From: "Sisyphus" <[EMAIL PROTECTED]> To: "inline" <inline@perl.org> Sent: Wednesday, May 31, 2006 5:47 PM Subject: Re: problem with LIBS
> > ----- Original Message ----- > From: "Todd H" <[EMAIL PROTECTED]> > To: <inline@perl.org> > Sent: Tuesday, May 30, 2006 10:58 PM > Subject: Re: problem with LIBS > . > . > > > > 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" > > > > That is strange. I agree with your diagnosis that subsequent calls are > wiping out the INC setting - but that is something that simply should *not* > happen (afaik). > Yes - I was right about that. From 'perldoc Inline': -- quote-- The Config options are inherited and additive. You can use as many Config calls as you want. -- end quote -- At least, that's what the documentation says. But, like Todd, I find that they are not "additive" - subsequent Config calls are wiping out config options set by earlier Config calls. I'm fairly sure it wasn't always like that - but now I'm finding the same on both perl 5.8.8 and perl 5.6.1. Todd, I think the simplest thing to do is to follow the advice from my earlier post: > I guess you could try with just *one* 'use Inline C => Config =>.....' as > follows: > > use Inline C => Config => > INC => '-I C:/MyCode/INCS', > LIBS => '-L C:/MyCode/LIBS -lolimg32', > BUILD_NOISY => 1; > That should work (and should also work with spaces in directory names if you observe the same usage of double quotes that you presented in your first post). Cheers, Rob
