How can I check this?
binutils is our friend :)
I think the problem is not as much the imported functions from the
windows unit, although that is interesting too, but more the used
functions / procedures and methods from the classes unit. Do you know
how I can check, that things are lef
Oro06 wrote:
using -CX, rtl built fine .a are created
then progs compiled with $SMARTLINK ON
compile and run
Do you see any difference when you using smartlinking or not?
I tried the following test program:
program Project1;
{$mode objfpc}{$H+}
uses
Windows, Classes
{ ad
using -CX, rtl built fine .a are created
then progs compiled with $SMARTLINK ON
compile and run
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel
Daniël Mantione wrote:
>
> Op Tue, 16 May 2006, schreef Vincent Snijders:
>
>> Hi,
>>
>> I was testing how bin arm-wince lcl applications are and wanted to test with
>> smartlinking.
>>
>> First try: using LD as linker
>> This didn't work, because even if I do make rtl OPT="-CX", no lib*.a files
Op Tue, 16 May 2006, schreef Vincent Snijders:
> Hi,
>
> I was testing how bin arm-wince lcl applications are and wanted to test with
> smartlinking.
>
> First try: using LD as linker
> This didn't work, because even if I do make rtl OPT="-CX", no lib*.a files are
> created.
>
> Second try: u
Hi,
I was testing how bin arm-wince lcl applications are and wanted to test with
smartlinking.
First try: using LD as linker
This didn't work, because even if I do make rtl OPT="-CX", no lib*.a files are
created.
Second try: using internal linker, which presumably doesn't need the lib*.a fil
