Re: [fpc-pascal] Resource compilation

Am 25.09.2017 um 14:24 schrieb Sven Barth via fpc-pascal: > The RC language itself isn't *that* difficult. Main difficulty would be to > essentially implement a C-preprocessor-compatible preprocessor. As I have just discovered, the installer provides a (rather antique) gcc on Windows and depends on

Re: [fpc-pascal] compiler option for $J directive

Am 11.10.2017 05:12 schrieb "Mr Bee via fpc-pascal" < fpc-pascal@lists.freepascal.org>: > > 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

Re: [fpc-pascal] compiler option for $J directive

Am 11.10.2017 07:00 schrieb "Mr Bee via fpc-pascal" < fpc-pascal@lists.freepascal.org>: > > 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 a

Re: [fpc-pascal] compiler option for $J directive

>> 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 -

Re: [fpc-pascal] compiler option for $J directive

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

Re: [fpc-pascal] compiler option for $J directive

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 ___ fpc-pascal mail

Re: [fpc-pascal] no fpc.exe file after installation

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 is.

Re: [fpc-pascal] no fpc.exe file after installation

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 install

Re: [fpc-pascal] no fpc.exe file after installation

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 stil

Re: [fpc-pascal] alternative name fpc cross

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 ppccrossarm and units > arm-embedded

Re: [fpc-pascal] alternative name fpc cross

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 an

Re: [fpc-pascal] alternative name fpc cross

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 ,

Re: [fpc-pascal] alternative name fpc cross

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 creat

Re: [fpc-pascal] alternative name fpc cross

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 a

Re: [fpc-pascal] alternative name fpc cross

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 embarrassi

Re: [fpc-pascal] alternative name fpc cross

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 > co

Re: [fpc-pascal] getting cross with the cross compiler

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 under

Re: [fpc-pascal] alternative name fpc cross

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 spe

Re: [fpc-pascal] getting cross with the cross compiler

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 whe

Re: [fpc-pascal] getting cross with the cross compiler

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  tha

Re: [fpc-pascal] getting cross with the cross compiler

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 perfect

Re: [fpc-pascal] getting cross with the cross compiler

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. You are trying to build

Re: [fpc-pascal] alternative name fpc cross

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 spec

Re: [fpc-pascal] getting cross with the cross compiler

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 3.

Re: [fpc-pascal] getting cross with the cross compiler

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 built with 3.0.2 , it see

Re: [fpc-pascal] compiler option for $J directive

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 variables (cause that is ho

Re: [fpc-pascal] no fpc.exe file after installation

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

Re: [fpc-pascal] no fpc.exe file after installation

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 list

Re: [fpc-pascal] alternative name fpc cross

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 different

Re: [fpc-pascal] getting cross with the cross compiler

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 could

Re: [fpc-pascal] no fpc.exe file after installation

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 _

Re: [fpc-pascal] no fpc.exe file after installation

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,

[fpc-pascal] alternative name fpc cross

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/ ___ fpc-

Re: [fpc-pascal] no fpc.exe file after installation

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 installation

Re: [fpc-pascal] compiler option for $J directive

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 support it, or there mus