Terry, Obviously you can't give us the dlls of interest, but do you have some simple dynamic libraries that demonstrate the problem? Or have you tried linking to multiple system libraries and encountered the same problem, for example? If so, could you reply with the error logs as an attachment?
Also, what compiler are you using with ActiveState? David On Nov 23, 2011 3:45 AM, "W. Terry Hardgrave" <wter...@verizon.net> wrote: > Inline Mailing List-- > > First I am a newbie to Inline::C with lots of experience with both the > original > Bell Labs C plus lots of experience with Perl. > > I was able to get Inline::C working fine until I tried to link in the DLLs. > > I was reading several documents including: > > http://www.foo.be/docs/tpj/**issues/vol5_3/tpj0503-0005.**html<http://www.foo.be/docs/tpj/issues/vol5_3/tpj0503-0005.html> > > plus Inline::C and inline::Configuration documentation, but I am still > unclear on the syntax to > link multiple DLLs. > > Here is my latest try which still does not find the external references: > > use Inline C => Config => LIBS => '-LC:\workspace\work\inline -lX1 -lX2'; > > where X1.dll and X2.dll (not the real names) > are in the directory C:\workspace\work\inline > > I tried to use the Begin block from the reference above, but I could not > find > Inline::Config in Activestate PPM list. > > If someone can suggest the correct syntax, suggest the best place to store > the DLLs > for automatic access, or point to additional documentation, I would > certainly appreciate it. > > In general, I am trying to wrap third-party proprietary APIs for use > within ActiveState Perl. > > Thanks, Terry > > ============================ > > W. Terry Hardgrave > Bethesda, MD > wter...@verizon.net > 301-873-4440 (mobile) >
