[Lazarus] Lazarus 2.0.2 EditorMacroScript error on first startup RPi4B

[Martin Frb]

On 18/08/2019 23:58, Bo Berglund via lazarus wrote:
> On Sun, 18 Aug 2019 22:51:31 +0200, Martin Frb via lazarus
> <lazarus at lists.lazarus-ide.org> wrote:
>
>> On 18/08/2019 21:19, Bo Berglund via lazarus wrote:
>>> Parameter type not implemented!
>>>
>> So on arm that explains the error.
>> It does not implement passing a set as param (must be set, since string
>> worked in other tests).
> Does this mean that FPC on Arm is not generating the expected code
> like it does on Windows? So the cross-platform operation is somewhat
> broken?
No, it means PascalScript is not fully implemented

>> I have to see, if there are any options.
>> Otherwise I will disable it for arm (since it does not currently work
>> for anyone, it would not be a regression)
>>
>> As for what happened on windows, no idea.
> I think I have seen the same first start error for a long time on the
> RPi. It is quite possible that I don't have the complete set of
> required packages listed for installation in my script and this is
> what breaks it. But that is provided that it is not an fpc deviation
> for arm of course.
>
> On Windows I have yet to build a dev system myself, I always use the
> "official" installers there.
It is not a missing package.
All the code is compiled into the IDE.

PascalScript is a 3rd party package. It includes some asm code that 
differs for each platform (cpu and general type of OS).

The OS type only matters because the calling convention differs. That is 
fpc (following the rules for each platform) uses different registers to 
store function param.
But there is no diff between win7 (64bit) and win10 (64bit). So if it 
works on w10 for me, I have no idea why it fails for you (win 7).

Arm/linux (raspi) has different code in PS. And apparently that is 
incomplete. But that only affects RPI.

Also on either system. After the error happens once, that is stored in 
the config. Unless you remove your config each time that you install, 
you should never see the error again.
To verify that, you can (after the error) check the XML file. That xml 
file should stay there forever.

As I said, I will decide (soon / hopefully sometime before the next 
release) what to do on arm. Maybe disable it for arm. Then there wont be 
an error.
Maybe I find a work around. Then I would have to ask you to test (since 
I cant currently).