Re: Problem linking with an import library (.lib) file:

On 5/16/2015 04:08, Mark Rivers wrote: > Jon Y wrote: > >> Try using gendef to generate a def file from the DLL and use dlltool to >> generate an import library from the new def file. > > Unfortunately the dll is stripped, so this does not work: > > $ nm plxapi631.dll > nm: plxapi631.dll: no sym

RE: Problem linking with an import library (.lib) file:

Jon Y wrote: > Try using gendef to generate a def file from the DLL and use dlltool to > generate an import library from the new def file. Unfortunately the dll is stripped, so this does not work: $ nm plxapi631.dll nm: plxapi631.dll: no symbols I know that this specific .lib file has worked in

Re: Problem linking with an import library (.lib) file:

On 5/14/2015 22:47, Mark Rivers wrote: > Additional information: > > - This is Cygwin 2.0.1, 32-bit on a Windows 7 64-bit machine. > > The "file" utility claims it is an archive file: > $ file ../../lib/cygwin-x86/PlxApi.lib > ../../lib/cygwin-x86/PlxApi.lib: current ar archive Try using gendef

RE: Problem linking with an import library (.lib) file:

Additional information: - This is Cygwin 2.0.1, 32-bit on a Windows 7 64-bit machine. The "file" utility claims it is an archive file: $ file ../../lib/cygwin-x86/PlxApi.lib ../../lib/cygwin-x86/PlxApi.lib: current ar archive The "nm" utility appears to interpret the file OK: rivers@rivers-mobi