On 12/05/18 23:55, Jesus Reyes A. via Lazarus wrote:
En Fri, 11 May 2018 08:40:28 -0500, patspiper via Lazarus
escribió:
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't
I am not sure if this will help, but I place this script as "setup" in any
fpc directory:
#!/bin/bash
if [ -z ${OLDPATH+x} ]; then
OLDPATH=$PATH
else
PATH=$OLDPATH
fi
BASE="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
export PPC_CONFIG_PATH=$BASE/bin
rm $PPC_CONFIG_PATH/fpc.cfg > /dev/
En Fri, 11 May 2018 08:40:28 -0500, patspiper via Lazarus
escribió:
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't think this is an improvement. For new users this
l
On 12/05/18 11:34, Michael Ring via Lazarus wrote:
Do you have plans to make it possible to switch debuggers in the same
plugin, too?
No, as switching debuggers is already possible in the debugging section.
This would be very helpful for embedded targets, it is always a pain
to reconfigure gd
Do you have plans to make it possible to switch debuggers in the same
plugin, too?
This would be very helpful for embedded targets, it is always a pain to
reconfigure gdb when switching between an embedded and a native target.
Could it also be possible to make this plugin project based?
Loo
On 11/05/18 16:17, Joost van der Sluis via Lazarus wrote:
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't think this is an improvement. For new users this
looks like a nightmare. It should be hidden, at least, imho. Or
better: ma
On 05/11/2018 03:26 PM, Mattias Gaertner via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't think this is an improvement. For new users this
looks like a nightmare. It should be hidden, at least, imho. Or better:
make it a plugin.
This is a plugin.
In that case: nothi
On Fri, 11 May 2018 15:17:45 +0200
Joost van der Sluis via Lazarus wrote:
> On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
> >
> > Attached snapshot is work in progress
>
> Sorry, but I don't think this is an improvement. For new users this
> looks like a nightmare. It should be hidden
On 05/10/2018 04:35 PM, patspiper via Lazarus wrote:
Attached snapshot is work in progress
Sorry, but I don't think this is an improvement. For new users this
looks like a nightmare. It should be hidden, at least, imho. Or better:
make it a plugin.
Regards,
Joost.
--
___
Le 10/05/2018 à 14:31, Joost van der Sluis via Lazarus a écrit :
Op 10-05-18 om 14:05 schreef Giuliano Colla via Lazarus:
Il 09/05/2018 12:34, Joost van der Sluis via Lazarus ha scritto:
That's more a hack then a solution
I fail to grasp why startlazarus should be a feature, and fpc.sh
shoul
On 07/05/18 17:54, Gabor Boros via Lazarus wrote:
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machine from scratch with RHEL 7.5
on it and try to utilize FPC trunk too (with La
On 07/05/18 17:54, Gabor Boros via Lazarus wrote:
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machine from scratch with RHEL 7.5
on it and try to utilize FPC trunk too (with La
On Thu, 10 May 2018, Joost van der Sluis via Lazarus wrote:
Oh, you may do so. But it is unnecessary and confusing in the fpc-case.
Off-course you can configure Lazarus to use fpc.sh. But what do you do
in a terminal? Wouldn't it be easier to just call 'fpc_304' and
'fpc_trunk'? Or /path/t
Op 10-05-18 om 14:05 schreef Giuliano Colla via Lazarus:
Il 09/05/2018 12:34, Joost van der Sluis via Lazarus ha scritto:
That's more a hack then a solution
I fail to grasp why startlazarus should be a feature, and fpc.sh should
be a hack.
Startlazarus is also a hack, because on Windows you
Il 09/05/2018 12:34, Joost van der Sluis via Lazarus ha scritto:
That's more a hack then a solution
I fail to grasp why startlazarus should be a feature, and fpc.sh should
be a hack.
Having multiple fpc.cfg files, as it may be required by multiple fpc
installations requires invoking the com
That's more a hack then a solution, and the real solution is simple and
also works outside Lazarus: place the fpc.cfg in ~/experiments/etc,
~/development/etc etc, as already suggested by Ingo. Or, even better,
just alongside the compiler-executable. You can call 'fpc -v
On 09/05/18 10:45, Joost van der Sluis via Lazarus wrote:
Op 08-05-18 om 13:46 schreef Giuliano Colla via Lazarus:> E.G. you may
have a full tree (fpc+Lazarus) in ~/development/ another > one in
~/production and a third one in ~/experiments. The main trick, as > far
as fpc is concerned, is to h
Op 08-05-18 om 13:46 schreef Giuliano Colla via Lazarus:
E.G. you may have a full tree (fpc+Lazarus) in ~/development/ another
one in ~/production and a third one in ~/experiments. The main trick, as
far as fpc is concerned, is to have as fpc executable an fpc.sh (a name
which is accepted by La
Il 07/05/2018 16:54, Gabor Boros via
Lazarus ha scritto:
Hi All,
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machi
Am 07.05.2018 um 16:54 schrieb Gabor Boros via Lazarus:
Is BigChimp's suggestion (1.-6.) a good starting point nowadays or
something changed meanwhile in this topic. I will build everything
(Lazarus fixes_1_8 and trunk, FPC trunk) from source except the actual
stable FPC (now 3.0.4).
https://
Hi All,
My main development toolset is FPC 3.0.4 and Lazarus fixes_1_8.
Sometimes I try some things with Lazarus trunk also. It is easy.
But now build up a new development machine from scratch with RHEL 7.5 on
it and try to utilize FPC trunk too (with Lazarus trunk). I use
"--primary-config-pa
21 matches
Mail list logo
