All I got is http://www.freepascal.org/docs-html/ref/refse5.html
it gives this example:
Const
AConst = 12 deprecated;
var
p : integer platform;
Function Something : Integer; experimental;
So deprecated after a variable, or constant, does NOT have a semicolon.
Indeed
Const AConst =
On 11 Mar 2010, at 19:46, Rob Kennedy wrote:
> I've installed FPC from the fpc-2.4.0.intel-macosx.dmg package on
> SourceForge, and I'm trying to compile code into a 64-bit program. I
> can't find the command-line option to make that happen, though. How do
> I make it generate 64-bit code on my I
I've installed FPC from the fpc-2.4.0.intel-macosx.dmg package on
SourceForge, and I'm trying to compile code into a 64-bit program. I
can't find the command-line option to make that happen, though. How do
I make it generate 64-bit code on my Intel Mac?
--
Rob
_
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
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.
i use cross-compiling from win32 to (target)linux...
and get this error; "Recompiling BaseUnix, checksum changed for System"
*** i read this doc:
http://wiki.freepascal.org/Releasing_units_without_source_code
*** but, i cant...
i am using this snapshot:
ftp://ftp.freepascal.org/pub/fpc/snapshot/v
On Thu, Mar 11, 2010 at 8:15 AM, Bernd Mueller wrote:
> it looks, as if 2.4.x was not so well tested on Wince. Perhaps you could run
> the test suite and see if it is a compiler problem.
How can I do this?
--
Felipe Monteiro de Carvalho
___
fpc-pascal
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
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
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
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.
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
Felipe Monteiro de Carvalho wrote:
What do you recommend? Simply creating a report?
http://www.freepascal.org/testsuite/cgi-bin/testsuite.cgi?os=17&cpu=6&version=0&date=
it looks, as if 2.4.x was not so well tested on Wince. Perhaps you could
run the test suite and see if it is a compiler pr
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
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?
_
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
Hello,
Who maintains the wince port and the arm port?
Some users are experiencing a very wierd bug in wince-arm which
happens in pure lcl app or kol app + lnet (no idea what the common
factor is). It also happens in some devices, but not all of them and
acording to the reports it doesn't happen i
17 matches
Mail list logo
