>> They were used mainly back at TP times to have procedure local static
variables (cause that is how they behave as inside procedures).
>
> Can we make the {$J-} as default in fpc and objfpc mode for the next
major release?
+1
___
fpc-pascal maillist
2017-10-10 16:21 GMT+07:00 Sven Barth via fpc-pascal <
fpc-pascal@lists.freepascal.org>:
> They were used mainly back at TP times to have procedure local static
> variables (cause that is how they behave as inside procedures).
>
Can we make the {$J-} as default in fpc and objfpc mode for the next
2017-10-10 13:28 GMT+07:00 Marco van de Voort :
>
> Since it is already largely uploaded, no. We are only waiting on some
> targets.
>
I thought such a minor fix that don't break any codes could be included.
--
Regards,
–Mr Bee
Am 10.10.2017 um 21:17 schrieb Graeme Geldenhuys:
> On 2017-10-10 19:54, Florian Klämpfl wrote:
>> Well, lack of manpower is not that odd:)
>
> Isn't building the installations automated tasks?
No. As building is not the main work, but creating, maintaining and testing the
installer scripts
On 2017-10-10 19:54, Florian Klämpfl wrote:
Well, lack of manpower is not that odd:)
Isn't building the installations automated tasks? So reallocate the man
power for creating the win64 cross-compiler, and let them rather spend
the time on creating a native 64-bit Windows compiler and
Am 10.10.2017 um 09:06 schrieb Graeme Geldenhuys:
> On 2017-10-09 09:56, adrian.soentger...@web.de wrote:
>> i installed “fpc-3.0.2.i386-win32.cross.x86_64-win64” on my laptop with
>> windows 7, but there seem
>> to be no fpc.exe file, so i can´t compile.
>
> For some odd reason the FPC team
Am 10.10.2017 15:21 schrieb "turro75" :
>
> Well,
>
> I think my problem is easier
> when I compile fpc for arm-android target I get ppccrossarm and units
> arm-android (with binutils arm-linux-android-*)
>
> when I compile fpc for arm-embedded target I get
On 10/10/17 13:50, pasc...@piments.com wrote:
On 10/10/17 13:29, Karoly Balogh (Charlie/SGR) wrote:
Linux Subsystem for Windows.
While I know what you mean ...
I used to be maintainer on Wine AppDB for several years. Nothing ever
worked from one release to the next. WINE spent 10y as
Hi,
On Tue, 10 Oct 2017, Michael Van Canneyt wrote:
> > I used to be maintainer on Wine AppDB for several years. Nothing ever
> > worked from one release to the next. WINE spent 10y as an alpha
> > release and it started to get embarrassing so they called it beta.
> > Everything still, broke ,
Well,
I think my problem is easier
when I compile fpc for arm-android target I get ppccrossarm and units
arm-android (with binutils arm-linux-android-*)
when I compile fpc for arm-embedded target I get ppccrossarm and units
arm-embedded (with binutils arm-none-eabi-*)
both are able to
On Tue, 10 Oct 2017, pasc...@piments.com wrote:
On 10/10/17 13:29, Karoly Balogh (Charlie/SGR) wrote:
Linux Subsystem for Windows.
While I know what you mean ...
I used to be maintainer on Wine AppDB for several years. Nothing ever
worked from one release to the next. WINE spent 10y
On 10/10/17 13:29, Karoly Balogh (Charlie/SGR) wrote:
Linux Subsystem for Windows.
While I know what you mean ...
I used to be maintainer on Wine AppDB for several years. Nothing ever
worked from one release to the next. WINE spent 10y as an alpha
release and it started to get
Hi,
On Tue, 10 Oct 2017, pasc...@piments.com wrote:
> > The compiler is *NOT* OS/platform specific, only CPU specific. Use any for
> > both, and specify the right target using -Tandroid or -Tembedded when
> > invoking.
>
> Maybe you meant the compiler is not TARGET OS specific in that it can
>
On 10/10/17 10:08, Tony Whyman wrote:
On 10/10/17 05:51, pasc...@piments.com wrote:
Were it not for the version restrictions in building fpc one could
arguably say this was a reasonable assumption. As it is, it leads to
a very confused and confusing state which has taken several days to
On 10/10/17 11:16, Karoly Balogh (Charlie/SGR) wrote:
Hi,
On Tue, 10 Oct 2017, turro75 wrote:
when I create the cross compiler to arm-android and arm-embedded I get the
same compiler name so unable to have both running in the same system.
any workaround?
The compiler is *NOT* OS/platform
In our previous episode, pasc...@piments.com said:
y> > release compiler (currently 3.0.0 or 3.0.2) is supported.
> >
> > Regards,
> > Sven
>
> You were mis-reading what I meant. I know it is supposed to complain
> when I use 3.1.1 , my point was the messages said I should ONLY use
> 3.0.0
On 10/10/17 10:35, Tony Whyman wrote:
On 10/10/17 05:51, pasc...@piments.com wrote:
$make all NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64
INSTALL_PREFIX=/usr
Makefile:2914: *** The only supported starting compiler version is
3.0.0. You are trying to build with 3.1.1.. Stop.
BTW is
On 10/10/17 10:08, Tony Whyman wrote:
Within the Lazarus parts of the libraries, the Linux libs have the gtk2
interface libraries, while the Windows ones have the win32 interfaces
libraries (both win32 and win64).
Thanks, that was the missing element.
I dropped using gtk2 and it works
On 10/10/17 10:25, Sven Barth via fpc-pascal wrote:
Am 10.10.2017 08:08 schrieb >:
> $make all NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64
INSTALL_PREFIX=/usr
> Makefile:2914: *** The only supported starting compiler version is
3.0.0.
Hi,
On Tue, 10 Oct 2017, turro75 wrote:
> when I create the cross compiler to arm-android and arm-embedded I get the
> same compiler name so unable to have both running in the same system.
> any workaround?
The compiler is *NOT* OS/platform specific, only CPU specific. Use any for
both, and
On 10/10/17 05:51, pasc...@piments.com wrote:
$make all NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64
INSTALL_PREFIX=/usr
Makefile:2914: *** The only supported starting compiler version is
3.0.0. You are trying to build with 3.1.1.. Stop.
BTW is that msg is correct? I just built with
Am 10.10.2017 08:08 schrieb :
> $make all NOGDB=1 OS_TARGET=linux CPU_TARGET=x86_64
INSTALL_PREFIX=/usr
> Makefile:2914: *** The only supported starting compiler version is 3.0.0.
You are trying to build with 3.1.1.. Stop.
>
> BTW is that msg is correct? I just
Am 10.10.2017 08:49 schrieb :
> BTW why would anyone want
> {$WRITEABLECONST ON}
>
> writable constants is an oxymoron and goes against the whole philosophy
of strict types which is central to Pascal.
They were used mainly back at TP times to have procedure local static
On 2017-10-10 10:10, Tomas Hajny wrote:
If you read the original post up to the end,
Ah, my bad.
Regards,
Graeme
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
On Tue, October 10, 2017 11:08, Graeme Geldenhuys wrote:
> On 2017-10-10 10:00, Tomas Hajny wrote:
>> Apparently, Graeme forgot to include you in Cc:; including you in my
>> follow-up now...
>
> Why must I CC him as well? I simply press "Reply" and all my replies go
> to the fpc-pascal mailing
On Tue, October 10, 2017 10:13, turro75 wrote:
Hi,
> when I create the cross compiler to arm-android and arm-embedded I get the
> same compiler name so unable to have both running in the same system.
> any workaround?
Are the two cross-compilers compiled with different options, or for
On 10/10/17 05:51, pasc...@piments.com wrote:
Were it not for the version restrictions in building fpc one could
arguably say this was a reasonable assumption. As it is, it leads to
a very confused and confusing state which has taken several days to
understand and untangle.
Maybe that
On 2017-10-10 10:00, Tomas Hajny wrote:
Apparently, Graeme forgot to include you in Cc:; including you in my
follow-up now...
Why must I CC him as well? I simply press "Reply" and all my replies go
to the fpc-pascal mailing list. Just like I've done with this email.
Regards,
Graeme
On Tue, October 10, 2017 09:06, Graeme Geldenhuys wrote:
> On 2017-10-09 09:56, adrian.soentger...@web.de wrote:
Hello,
Apparently, Graeme forgot to include you in Cc:; including you in my
follow-up now...
>> i installed “fpc-3.0.2.i386-win32.cross.x86_64-win64” on my laptop with
>> windows 7,
Hi All,
when I create the cross compiler to arm-android and arm-embedded I get the
same compiler name so unable to have both running in the same system.
any workaround?
Regards
--
Sent from: http://free-pascal-general.1045716.n5.nabble.com/
___
On 2017-10-09 09:56, adrian.soentger...@web.de wrote:
i installed “fpc-3.0.2.i386-win32.cross.x86_64-win64” on my laptop with windows
7, but there seem to be no fpc.exe file, so i can´t compile.
For some odd reason the FPC team still don't produce a native 64-bit
Windows compiler
On Tue, Oct 10, 2017 at 9:33 AM, wrote:
> Now a patch has been integrated for this , perhaps it could be added to
> Lazarus Project Options | Compiler Options | Parsing
Patches are welcome also for that.
The option must be either hidden for compiler versions that do not
Also, what's the difference between TBufDataset and TMemDataset?
Aren't they both in-memory datasets? If so, why do we have two
different components for the same thing?
As Michael wrote TMemDataSet is older.
And I add that it is also much "lighter". So for somebody who does not
need
Hello,
i installed “fpc-3.0.2.i386-win32.cross.x86_64-win64” on my laptop with windows
7, but there seem to be no fpc.exe file, so i can´t compile.
In which folder should this file be? Where can i get it from?
Thanks for your answer!
Adrian
P.S.: I am not subscribed to a mailing
On 08/10/17 21:24, leledumbo via fpc-pascal wrote:
There is my old feature request about it
https://bugs.freepascal.org/view.php?id=30344 :) You can monitor it.
No one seems to care to implement it, so if you badly need it: sj.patch
In our previous episode, Mr Bee via fpc-pascal said:
> Thank you, both to Leledumbo and Sven. Will this patch be available in the
> next FPC v.3.0.4 release?
Since it is already largely uploaded, no. We are only waiting on some
targets.
___
fpc-pascal
2017-10-08 23:17 GMT+07:00 Marcos Douglas B. Santos :
>
> Most developers are using single .inc file that contains all
> directives for the whole project.
>
Well, I don't like such approach. I prefer using my own shell script that I
can configure for many purposes and
On 08/10/17 10:12, Tomas Hajny wrote:
On Sat, October 7, 2017 22:13, pasc...@piments.com wrote:
Hi,
.
.
Can you offer any insights into what is going on with Lazarus not
locating the system unit and friends. As you acknowledge they are
treated somewhat differently due to problems with
Thank you, both to Leledumbo and Sven. Will this patch be available in the next
FPC v.3.0.4 release?
–Mr Bee
Pada Selasa, 10 Oktober 2017 04.44.44 WIB, Sven Barth via fpc-pascal
menulis:
Am 08.10.2017 22:24 schrieb "leledumbo via fpc-pascal"
39 matches
Mail list logo