Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Marco van de Voort
In our previous episode, Adriaan van Os said: > >> Well, then the linker complains about unresolved symbols. > > > > You have to mention the name of the dll in the procedure declaration: > > > > procedure test; stdcall; external 'dllname'; > > I assume ".dll" is added only if "dllname" doesn't h

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Tomas Hajny
On Thu, March 11, 2010 15:28, Adriaan van Os wrote: > Jonas Maebe wrote: >> On 11 Mar 2010, at 12:28, Adriaan van Os wrote: >> >>> Marco van de Voort wrote: In our previous episode, Adriaan van Os said: > I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X > to Win32.

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Adriaan van Os
Jonas Maebe wrote: On 11 Mar 2010, at 12:28, Adriaan van Os wrote: Marco van de Voort wrote: In our previous episode, Adriaan van Os said: I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to Win32. This works fine, except that {$linklib xxx.dll} says dlls are usually not

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Tomas Hajny
On Thu, March 11, 2010 12:50, Jonas Maebe wrote: > On 11 Mar 2010, at 12:28, Adriaan van Os wrote: >> Marco van de Voort wrote: >>> In our previous episode, Adriaan van Os said: I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to Win32. This works fine, except that {$l

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Tomas Hajny
On Thu, March 11, 2010 12:28, Adriaan van Os wrote: > Marco van de Voort wrote: >> In our previous episode, Adriaan van Os said: >>> I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to >>> Win32. This works fine, >>> except that {$linklib xxx.dll} says >> >> dlls are usually not

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Jonas Maebe
On 11 Mar 2010, at 12:28, Adriaan van Os wrote: Marco van de Voort wrote: In our previous episode, Adriaan van Os said: I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to Win32. This works fine, except that {$linklib xxx.dll} says dlls are usually not $linklib'ed in FPC.

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Adriaan van Os
Marco van de Voort wrote: In our previous episode, Adriaan van Os said: I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to Win32. This works fine, except that {$linklib xxx.dll} says dlls are usually not $linklib'ed in FPC. What happens if you simply omit the linklib? We

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread cobines
Shouldn't the import library for "XXX.dll" be named "libXXX.a"? I remember that linking to ".lib" didn't work for me, but to ".a" did. -- cobines ___ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc

Re: [fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Marco van de Voort
In our previous episode, Adriaan van Os said: > I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to > Win32. This works fine, > except that {$linklib xxx.dll} says dlls are usually not $linklib'ed in FPC. What happens if you simply omit the linklib? _

[fpc-pascal] -Twin32 linker woes

2010-03-11 Thread Adriaan van Os
I am cross compiling with fpc svn trunk and -Twin32 on i386 Mac OS X to Win32. This works fine, except that {$linklib xxx.dll} says error: 1: Import library not found for xxx Same result with {$linklib xxx}. The dll (and dll.lib) are absolutely there, {$linklib xxx.dll.lib} says