Closed DUOLabs333 closed 6 months ago
Maybe Laz is old. Use 3.2.
anyway, comment this line
{$ifdef LCLQT5}
//if you use Lazarus 2.x, this line cannot be compiled, so comment it
QTimer_singleShot(10, @_QtDelayTimeOut);
{$endif}
it is check that runtime Qt5 lib is correct. if it is not, on calling SaveAs dialog, app will crash.
Commenting out that line got me to linking. Unfortunately, I get the same error I got before: undefined reference to __libc_csu_init. This is likely due to fpc not finding crtbegin.o, even though it's already installed on my system.
What FPC version? try to use the last release. If not ok, try the 'trunk' (last in git). Use the fpcUpDeluxe and set there the 'trunk' option to use last git version.
Ok, so it turns out that on Arch Linux ARM, Lazarus is outdated by more than 2 years (though fpc is up to date).
fpcUpDeluxe will ignore that sad fact, it can install any last version.
Hmmm, it turns out that compiling lazbuild fails with the same error.
It turns out the fix for fpc is in 3.2.4, which means I have to recompile that too. Is it possible for cudatext_up to point to a custom fpc directory, like with lazbuild?
it don't support FPC path yet. try to fork it:
--lazdir
cmdline param--compiler=<ppcXXX>
param --> add it pleaseInterestingly, if I change the compiler parameter to my locally compiled version, I get Can't find unit system used by emmet_package
for each of the packages used.
it means that fpc.cfg file is not fully configured. 'cannot find unit system' error means it. I guess here. not sure!
I'll try again soon and see if I can get it working this time.
Is there a way to set fpcdeluxe to do a shallow clone (ie, clone --depth 1
)?
Ok, I got it compiled using fpcupdeluxe!
Maybe my lazarus version (2.2.1) is too old?