On 8 Sep 08, at 9:34, Paul wrote:
Hi Paul,
.
.
> I know KOL uses api calls (used it years ago), but I prefer to create my
> forms, buttons etc. directly with api calls myself to keep the exe size as
> small as possible.
> My problem is: how should I write api call's for a different target pla
On 08 Sep 2008, at 08:57, Paul wrote:
"U kunt het programma lazarus.app niet openen, omdat het niet wordt
ondersteund door deze architecture"
translated:
"You can't open program lazarus.app, because it's not supported by
this architecture"
This issue is mentioned for a certain version of
aebe" <[EMAIL PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Monday, September 08, 2008 9:48 AM
Subject: Re: [fpc-pascal] Exe size
On 08 Sep 2008, at 08:34, Paul wrote:
After removing and installing, adding all folders manually, I got it
running and could even run a
In our previous episode, Jonas Maebe said:
>
>
> Please be more specific, because otherwise it is very hard to help.
> For an interesting essay on this, see
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Hehe, I really like the bit in red at the bottom.
__
On 08 Sep 2008, at 08:34, Paul wrote:
After removing and installing, adding all folders manually, I got it
running and could even run a small program.
Next day, I get a OS-message that Lazarus is not a regular mac
application and is now blocked (OS X 10.5)
Can you please give the exact err
Hi Tomas,
I don't know much about KOL, but if I understand it correctly, it's a
framework (GUI library if you like) allowing the programmer to use
Pascal classes for the various GUI elements. Implementation of these
classes uses then the native API calls provided by the particular
platform (Win3
On 6 Sep 08, at 11:08, Paul wrote:
Hi Paul,
> > Similarly to Felipe, I don't understand why this should be a bad news for
> > you or why this should mean that Visual Studio gave you something not
> > available with FPC (or what that "something" was in that case)... It looks
> > as if I either do
Hi Tomas,
Similarly to Felipe, I don't understand why this should be a bad news for
you or why this should mean that Visual Studio gave you something not
available with FPC (or what that "something" was in that case)... It looks
as if I either don't understand what you meant with the statement a
ri, 9/5/08, Tomas Hajny <[EMAIL PROTECTED]> wrote:
> From: Tomas Hajny <[EMAIL PROTECTED]>
> Subject: Re: [fpc-pascal] Exe size
> To: "FPC-Pascal users discussions"
> Date: Friday, September 5, 2008, 2:13 PM
> On Fri, September 5, 2008 08:51, Paul wrote:
&g
On Fri, September 5, 2008 08:51, Paul wrote:
Hi Paul,
>> If you use a (cross-)compiler for ARM target processor, the generated
>> binary will be indeed an ARM binary, of course (ready to run on an
>> ARM under the selected target OS - WinCE in your case). If targetting
>> WinCE OS, you can only
On Fri, Sep 5, 2008 at 4:26 AM, Paul <[EMAIL PROTECTED]> wrote:
> I know, but for a remote support system, I need to control the computer.
> For CE, it wil be very basic though.
What does "control the computer" mean? And how is that something that
VS can achieve and Lazarus cannot?
--
Felipe Mon
- Original Message -
From: "Marco van de Voort" <[EMAIL PROTECTED]>
Note that wince's api is a subset of winapi. And that VS will suffer from
that also.
I know, but for a remote support system, I need to control the computer.
For CE, it wil be very basic though.
Paul
In our previous episode, Paul said:
> > If you use a (cross-)compiler for ARM target processor, the generated
> > binary will be indeed an ARM binary, of course (ready to run on an
> > ARM under the selected target OS - WinCE in your case). If targetting
> > WinCE OS, you can only use WinCE RTL
Hi Tomas,
If you use a (cross-)compiler for ARM target processor, the generated
binary will be indeed an ARM binary, of course (ready to run on an
ARM under the selected target OS - WinCE in your case). If targetting
WinCE OS, you can only use WinCE RTL and/or other units prepared for
that ta
On 4 Sep 08, at 21:03, Paul wrote:
> If I understand correcly, it's the lcl that adds a huge part to the exe.
> Since I only use 1 small form, I could create it with api calls.
> But FPC for WinCE uses a crosscompiler, how do I have to implement this ?
> Are Windows api calls translated to ARM-cal
e:
> From: Paul <[EMAIL PROTECTED]>
> Subject: Re: [fpc-pascal] Exe size
> To: "FPC-Pascal users discussions"
> Date: Thursday, September 4, 2008, 4:03 PM
> If I understand correcly, it's the lcl that adds a huge
> part to the exe.
> Since I only use 1 sma
If I understand correcly, it's the lcl that adds a huge part to the exe.
Since I only use 1 small form, I could create it with api calls.
But FPC for WinCE uses a crosscompiler, how do I have to implement this ?
Are Windows api calls translated to ARM-calls ?
Paul
___
- Original Message -
From: "Graeme Geldenhuys" <[EMAIL PROTECTED]>
Alternatively, write your WinCE program in pure assembly language.
You should get fully function GUI apps at around 20-60 Kbytes. :-)
LOL, I don't think so: my Delphi program has only very basic GUI (fi chat)
which i
On 9/4/08, Marco van de Voort <[EMAIL PROTECTED]> wrote:
> In our previous episode, Paul said:
> > Actually 1,16 MMb with 1 button and 1 label :-)
>
> http://wiki.freepascal.org/Size_Matters
>
> Pretty normal for a lazarus app. If you want minimal size, see the winapi
> demo in the examples.
- Original Message -
From: "Vincent Snijders" <[EMAIL PROTECTED]>
OK, you have a small size and a debuger crash. The debugger crash is ok,
because you "do not need a working debugger".
Indeed, only needed for testing but annoying though
Paul
_
http://wiki.freepascal.org/Size_Matters
Pretty normal for a lazarus app. If you want minimal size, see the winapi
demo in the examples.
I have this doc printed and it wont be a problen on Windows for which I have
the Delphi program.
I have not installed the WinCe version or crosscompiler, but
Paul schreef:
You cannot have both: a small size without debug info *and* a working
debugger.
I do not need a working debugger.
B: an executable that has a small size and can be released: disable
all debugging options (-g, -gl, -gh) and enable string (-Xs) in the
linking tab.
I've done tha
You cannot have both: a small size without debug info *and* a working
debugger.
I do not need a working debugger.
B: an executable that has a small size and can be released: disable all
debugging options (-g, -gl, -gh) and enable string (-Xs) in the linking
tab.
I've done that and also (-Og
In our previous episode, Paul said:
> Actually 1,16 MMb with 1 button and 1 label :-)
http://wiki.freepascal.org/Size_Matters
Pretty normal for a lazarus app. If you want minimal size, see the winapi
demo in the examples.
___
fpc-pascal maillist - f
Paul wrote:
> I'm testing with FPC/Lazrus on Windows now, but a simple program results in
> 11.5 MB size.
> I have enabled -Xs, -CX, -Og, -O2 in the project->compiler options
> (Lazarus), but the size is still the same.
> Anything else I should do?
Yes, you should also disable -gl option (Display
Actually 1,16 MMb with 1 button and 1 label and a debugger crash as a bonus
:-)
Paul
- Original Message -
From: "Florian Klaempfl" <[EMAIL PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Thursday, September 04, 2008 4:39 PM
Subject: Re: [fpc-pascal
Paul schreef:
I have to use:
C:\FPC\2.2.2\bin\i386-win32\strip.exe --strip-all
D:\FreePascal\Projects\Test\Project1.exe,
anything else fails.
In my Dutch version here, after compling is on the top position in that
compiler tab which is in fact before compling
Probably a translation bug.
Af
Paul schrieb:
> I have to use:
>
> C:\FPC\2.2.2\bin\i386-win32\strip.exe --strip-all
> D:\FreePascal\Projects\Test\Project1.exe,
> anything else fails.
>
> In my Dutch version here, after compling is on the top position in that
> compiler tab which is in fact before compling
> Probably a translat
and I have the same restrictions there.
Paul
- Original Message -
From: "Michael Fuchs" <[EMAIL PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Thursday, September 04, 2008 3:20 PM
Subject: Re: [fpc-pascal] Exe size
Paul schrieb:
I've read that, but
Paul schrieb:
I've read that, but isn't it suppose to work within the ide instead of
always start the cmd prompt and type in this ?
(or use a batch)
Project -> Compilersettings -> [Last Tab] -> Execute after
(I hope this is right, i've only the german version here).
Will this work for WinCE
L PROTECTED]>
To: "FPC-Pascal users discussions"
Sent: Thursday, September 04, 2008 3:07 PM
Subject: Re: [fpc-pascal] Exe size
Michael Fuchs schrieb:
I'm testing with FPC/Lazrus on Windows now, but a simple program results
in 11.5 MB size.
I have enabled -Xs, -CX, -Og, -O2 i
Michael Fuchs schrieb:
>> I'm testing with FPC/Lazrus on Windows now, but a simple program
results in 11.5 MB size.
>> I have enabled -Xs, -CX, -Og, -O2 in the project->compiler options
(Lazarus), but the size is still the same.
>> Anything else I should do?
>
> Use
> strip --strip-all $PR
Michael Fuchs schrieb:
I'm testing with FPC/Lazrus on Windows now, but a simple program
results in 11.5 MB size.
I have enabled -Xs, -CX, -Og, -O2 in the project->compiler options
(Lazarus), but the size is still the same.
Anything else I should do?
Use
strip --strip-all $PROGRAMNAME.exe
Paul schrieb:
I'm testing with FPC/Lazrus on Windows now, but a simple program results
in 11.5 MB size.
I have enabled -Xs, -CX, -Og, -O2 in the project->compiler options
(Lazarus), but the size is still the same.
Anything else I should do?
Use
strip --strip-all $PROGRAMNAME.exe
after
I'm testing with FPC/Lazrus on Windows now, but a simple program results in
11.5 MB size.
I have enabled -Xs, -CX, -Og, -O2 in the project->compiler options
(Lazarus), but the size is still the same.
Anything else I should do?
Paul
___
fpc-pascal
35 matches
Mail list logo
