On 01/27/2015 10:27 PM, Ewald wrote:
- Without the target system, the application cannot be tested ..
This is true, only because remote debugging is not well supported.
In fact I sometimes to programs to be run on a headless system (e.g. a
NAS) Here you can't install Lazarus, because you
Michael Schnell wrote:
On 01/27/2015 10:27 PM, Ewald wrote:
- Without the target system, the application cannot be tested ..
This is true, only because remote debugging is not well supported.
In fact I sometimes to programs to be run on a headless system (e.g. a
NAS) Here you can't
Am 28.01.2015 10:08 schrieb Björn Schreiber news...@drigus.de:
Am 27.01.2015 um 17:58 schrieb Marco van de Voort:
First narrow it down to the exact line that causes the problem. E.g. copy
relevant parts of sysutils into a program that only uses system, and then
start testing, till you know
On 01/28/2015 12:51 PM, Ewald wrote:
[this might be an extremely silly proposition, please forgive me] Why
don't you run lazarus through ssh? Or use vnc?
The (small) target system does not have any graphic-related stuff like
X, qt or gtk. So VNC, or remote X will not work.
Of course I can
Am 27.01.2015 um 17:58 schrieb Marco van de Voort:
First narrow it down to the exact line that causes the problem. E.g. copy
relevant parts of sysutils into a program that only uses system, and then
start testing, till you know which line provokes the problem.
What I can say at this time is
On 01/28/2015 10:01 AM, Michael Schnell wrote:
On 01/27/2015 10:27 PM, Ewald wrote:
- Without the target system, the application cannot be tested ..
This is true, only because remote debugging is not well supported.
For remote debugging a target system is needed as well? So even if
remote
Am 28.01.2015 um 11:21 schrieb Sven Barth:
As said by Marco: please try to reproduce it by copying parts of
SysUtils (e.g. GetLocaleStr) into an empty program (and using that code
of course ^^) to find an example code that shows the problem.
I narrowed it down to the following minimal
Using FPC v2.6.3 the {$WARNINGS OFF}, {$HINTS OFF}, and {$NOTES OFF}
directives affect all subsequently compiled units as well. That seems
wrong. Delphi limits the effects of those to the current compilation
unit, which is what I'd expect. Is this intentional?
Sample code:
Test.dpr
Hello.
I do main development on Linux 64.
For Windows, i use wine on Linux 64, (fpc.exe 32/64 installed without
problem) and compile the source via wine-fpc.exe.
The advantage is that you do not have to copy your source to a virtual
machine or a other native Windows.
And you may test your exe
Am 28.01.2015 22:17 schrieb Craig Peterson cr...@scootersoftware.com:
Using FPC v2.6.3 the {$WARNINGS OFF}, {$HINTS OFF}, and {$NOTES OFF}
directives affect all subsequently compiled units as well. That seems
wrong. Delphi limits the effects of those to the current compilation
unit, which
Am 28.01.2015 16:45 schrieb Björn Schreiber news...@drigus.de:
Am 28.01.2015 um 11:21 schrieb Sven Barth:
As said by Marco: please try to reproduce it by copying parts of
SysUtils (e.g. GetLocaleStr) into an empty program (and using that code
of course ^^) to find an example code that shows
11 matches
Mail list logo
