On 2017-12-30 15:16, coppolastudio via Lazarus wrote:
furthermore you can pack the executable with upx
That shouldn't be needed if debugging information is excluded from the
executable. Also from what I remember (years back), Windows anti-virus
software hated UPX compressed executables - givi
On Sat, Dec 30, 2017 at 12:52 PM, AlexeyT via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> fpc usually gives it (for my code, when i use "var" params).
>
You should see the warning with source file name and line number when you
recompile Cocoa LCL.
Can you please provide what the file name an
On 30.12.2017 20:51, Dmitry Boyarintsev via Lazarus wrote:
What line gives the warning?
fpc usually gives it (for my code, when i use "var" params).
--
Regards,
Alexey
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-
+procedure NSScrollerGetScrollInfo(docSz, pageSz: CGFloat; rl:
NSSCroller; Var ScrollInfo: TScrollInfo);
2) maybe better name parameters like ADocSize, APageSize, ARoller,
AScrollInfo like in LCL
--
Regards,
Alexey
--
___
Lazarus mailing list
L
On Sat, Dec 30, 2017 at 12:33 PM, AlexeyT via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:
> +procedure NSScrollerGetScrollInfo(docSz, pageSz: CGFloat; rl:
> NSSCroller; Var ScrollInfo: TScrollInfo);
>
> Pls use "out" instead of "var", because with "var" fpc gives warnings about
> not inited p
+procedure NSScrollerGetScrollInfo(docSz, pageSz: CGFloat; rl:
NSSCroller; Var ScrollInfo: TScrollInfo);
Pls use "out" instead of "var", because with "var" fpc gives warnings about not
inited parameter
--
Regards,
Alexey
--
___
Lazarus mailing lis
Il 30/12/2017 12:54, Bo Berglund via Lazarus ha scritto:
Because the server I use is located in Austin, Tx and I am in Sweden.
Have to use a VPN, which is not fast at all.
In that case you might consider:
1) To use git in place of svn. It is unbelievably fas
furthermore you can pack the executable with upx
Inviato tramite il client di Posta WPSIl Bo Berglund via Lazarus , 30/dic/2017 12:57 PM ha scritto:On Sat, 30 Dec 2017 13:34:41 +0200, Juha Manninen via Lazarus
wrote:
>How is svn import related to compiled binary siz
Am 30.12.2017 12:50 schrieb "Bo Berglund via Lazarus" <
lazarus@lists.lazarus-ide.org>:
On Sat, 30 Dec 2017 12:14:43 +0100 (CET), Michael Van Canneyt via
Lazarus wrote:
>> On Linux I am used to do "strip -s filename" on the resulting
>> executable to bring it down to a sensible size.
>> But on W
On Sat, 30 Dec 2017 13:34:41 +0200, Juha Manninen via Lazarus
wrote:
>How is svn import related to compiled binary size?
Because the server I use is located in Austin, Tx and I am in Sweden.
Have to use a VPN, which is not fast at all.
>Do you store the executable binary in revision control? Yo
On Sat, 30 Dec 2017 12:14:43 +0100 (CET), Michael Van Canneyt via
Lazarus wrote:
>> On Linux I am used to do "strip -s filename" on the resulting
>> executable to bring it down to a sensible size.
>> But on Windows 7, what can I do?
>
>You can do exactly the same. FPC is distributed with a strip
On Sat, Dec 30, 2017 at 1:07 PM, Bo Berglund via Lazarus
wrote:
> My little command line program (no GUI stuff at all) is bloated up to
> 7.7 Mbytes even though I have barely started work on it.
I believe there is debug info included.
If you compile with optimization and without debug info, the b
On Sat, 30 Dec 2017, Bo Berglund via Lazarus wrote:
I usually program with Lazarus on a Linux platform and with Delphi on
Windows.
But now I am working on a Lazarus 1.8.0/fpc3.0.4 IDE to make a
crossplatform program.
On Linux I am used to do "strip -s filename" on the resulting
executable to
I usually program with Lazarus on a Linux platform and with Delphi on
Windows.
But now I am working on a Lazarus 1.8.0/fpc3.0.4 IDE to make a
crossplatform program.
On Linux I am used to do "strip -s filename" on the resulting
executable to bring it down to a sensible size.
But on Windows 7, what
Am 30.12.2017 um 04:04 schrieb R0b0t1 via Lazarus:
>>
>> Debugging with gdbserver should work (server runs ok with app), if I had a
>> gdb for ppc64le on Windows.
>>
>> Any ideas ?
>>
>
> I have access to a ppc64le machine, but how did you build FPC for
> ppc64le? From x86_64, or?
For ppc64le, yo
I have build a cross-compiler for ppc64le from a win32 install with
fpcupdeluxe.
With this cross-compiler, ppc64le builds were made of fpc(laz)up.
Fpc(laz)up is a command line tool to install FPC (and Lazarus).
I used this to install FPC and Lazarus.
https://github.com/LongDirtyAnimAlf/Reiniero
16 matches
Mail list logo