Recent

Author Topic: Lazarus Release Candidate 1 of 2.2.0  (Read 70563 times)

Milsa

  • Sr. Member
  • ****
  • Posts: 261
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #75 on: August 24, 2021, 08:00:02 pm »
Will be a download for Windows arm64?

It is ideal for Raspberry Pi 400 with Windows 10.
I work with Lazarus 2.0.10, FPC 3.2.0, SVN 63526
This information is actual to: 1st Aug 2020

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7440
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #76 on: August 24, 2021, 08:54:13 pm »
Will be a download for Windows arm64?

Unfortunately not. We don't currently have anyone to build/test it.

Milsa

  • Sr. Member
  • ****
  • Posts: 261
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #77 on: August 25, 2021, 07:19:49 pm »
Does exist procedure on wiki how to build it? I will try to bulit it. For performance test (arm64 vs. x86-64 on ARM).

I will test Windows 11 on Raspberry Pi 400.
I work with Lazarus 2.0.10, FPC 3.2.0, SVN 63526
This information is actual to: 1st Aug 2020

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 7440
  • Debugger - SynEdit - and more
    • wiki
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #78 on: August 25, 2021, 10:58:33 pm »
Does exist procedure on wiki how to build it? I will try to bulit it. For performance test (arm64 vs. x86-64 on ARM).

I will test Windows 11 on Raspberry Pi 400.
Wiki: Not that I am aware of.

The scripts are in the repro/git: tools/installer/win. 


Marc

  • Administrator
  • Hero Member
  • *
  • Posts: 2530
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #79 on: August 26, 2021, 09:40:35 am »
Will be a download for Windows arm64?

It is ideal for Raspberry Pi 400 with Windows 10.

There are still issues with the compiler for win/arm64. I've not tried recently, but I don't think much has changed. Besides that it would require the latest trunk compiler.

Running Windows 11 on a rpi4 works reasonably ok, most of the hardware is supported (contrary to win10). Since the rpi doesn't meet the windows hardware requirements, you can only run the insider preview until it is released.

Windows 11 has a x86 and a x64 emulator, running x86 or x64 executables is surprisingly smooth

Marc
//--
{$I stdsig.inc}
//-I still can't read someones mind
//-Bugs reported here will be forgotten. Use the bug tracker

prof7bit

  • Full Member
  • ***
  • Posts: 139
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #80 on: September 01, 2021, 02:49:11 pm »
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

Probably a regression that nobody noticed because i cannot remember having seen this behavior in the past (but I cannot say when exactly it started happening because I'm not doing cross platform stuff every day).

I would not release before this is fixed.

dbannon

  • Hero Member
  • *****
  • Posts: 1604
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #81 on: September 03, 2021, 04:21:25 am »
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

Anyway, as I had just built a new build machine that does a lot of cross compiling thought I'd see if I could duplicate his/her issue. Not exactly but something close. This with FPC3.2.2 and Lazarus Trunk, the classic minimal project, that is, no attempt to alter mode, or invoke the cross compiler.  It seems to be associated with a message from Pango about "failed to create cairo scaled font, expect ugly output".  Not particularly ugly but not very informative.  See image below.

So, took the same lazarus trunk current source to my laptop, running the same OS, U20.04 Mate, built it and tested all OK.  Only difference between the two platforms is -
* The 'Build' machine is a fresh install and has cross compilers (to Windows 32/64, Linux 32 and RasPi) installed.
* The Laptop has no cross compilers but a longer history. 

So, it might be a cross compiler issue .....

Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

dsiders

  • Hero Member
  • *****
  • Posts: 520
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #82 on: September 03, 2021, 05:08:35 am »
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347
I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

main-2_3 is the development branch. It contains things have not been pulled into fixes_2_2  and included in lazarus_2_2_RC1.

lazarus_2_2_RC1 is a snapshot. It does not have the latest commits to fix errors in RC1.

fixes_2_2 has the commits that will be in lazarus_2_2-RC2 when it gets tagged and published.

Introducing, FPC 3.3.1 into the equation only muddies the waters. Version 2.2 is going to have the latest in the FPC 3.2.X series.

Anyway, as I had just built a new build machine that does a lot of cross compiling thought I'd see if I could duplicate his/her issue. Not exactly but something close. This with FPC3.2.2 and Lazarus Trunk, the classic minimal project, that is, no attempt to alter mode, or invoke the cross compiler.  It seems to be associated with a message from Pango about "failed to create cairo scaled font, expect ugly output".  Not particularly ugly but not very informative.  See image below.

So, took the same lazarus trunk current source to my laptop, running the same OS, U20.04 Mate, built it and tested all OK.  Only difference between the two platforms is -
* The 'Build' machine is a fresh install and has cross compilers (to Windows 32/64, Linux 32 and RasPi) installed.
* The Laptop has no cross compilers but a longer history. 

So, it might be a cross compiler issue .....

"trunk" is not a thing any more. Are you testing main-2_3, lazarus_2_2-RC1, or fixes_2_2? Clears as mud... right?
Lazarus 2.0.12, 2.2.0-RC1, 2.3.0 (Git) / FPC 3.2.0, 3.2.2 / x86-win64 / Windows 8.1

dbannon

  • Hero Member
  • *****
  • Posts: 1604
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #83 on: September 03, 2021, 08:08:29 am »
Yes, sorry, my language was imprecise.  I am using 'main', its not labeled any particular type of 'main'. I see it as the direct replacement of 'trunk'. See image.

I don't normally use the GUI side of Lazarus on my build machine, my build run is all command line. Maybe I need to run up Fixes_2_2, that would be far more relevant, its just that I had just finished building the (VM) machine, thought it useful to confirm or otherwise prof7bit's report. (and I did neither).

Davo
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

dbannon

  • Hero Member
  • *****
  • Posts: 1604
    • tomboy-ng, a rewrite of the classic Tomboy
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #84 on: September 03, 2021, 08:38:40 am »
Yes, I can confirm that Fixes_2_2 does the same thing, my sort of same thing, not prof7bit's.

So, the question is, is it because I am missing something in my install or is it, as prof7bit's experience (perhaps) suggests, an issue related to cross compiling ?  Personally, I cannot see what cross compiling has to do with it but the fact that no one else has yet picked it up says its medium rare, like cross compiling ...

Davo

Edit : I appear to have the same Pango and Cairo libraries and the Liberation Sans font installed on the laptop where I don't see this code tools issue, cannot see anything else relevant.
« Last Edit: September 03, 2021, 08:44:52 am by dbannon »
Lazarus 2, Linux (and reluctantly Win10, OSX)
My Project - https://github.com/tomboy-notes/tomboy-ng

prof7bit

  • Full Member
  • ***
  • Posts: 139
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #85 on: September 03, 2021, 06:19:10 pm »
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347

I am a little confused about versions here. Should we be testing against lazarus_2_2_0RC1 (which was tagged some time ago) or fixes_2_2 (which is still evolving) ?  prof7bit seems to be testing lazarus_2.3 and FPC3.3.1 ....

Yes, you spotted that correctly.

I have 2 installations on my workstation, usually using fixes-2.2 for daily work and I also have a trunk (main) installation around to see if a bug is already fixed in main or when I need to make a new branch for a merge request.

I first encountered this bug in fixes 2.2 (which is currently a bit ahead of 2.2RC1 and will eventually become 2.2). Then I tested it in main to verify it is not yet fixed there and behaves exactly the same in both branches, and then I made the bug report against main as usual (but I mentioned in the bug report it also affects 2.2).

Later while browsing this forum I thought to myself: 2.2 release is pretty damn close, it woluld be very ugly if it were released without first fixing this bug, so I mentioned it here because I know that the people who can make decisions are reading here.
« Last Edit: September 03, 2021, 06:59:31 pm by prof7bit »

prof7bit

  • Full Member
  • ***
  • Posts: 139
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #86 on: September 03, 2021, 06:35:32 pm »

main-2_3 is the development branch.

This is actually not a branch name, it is the name of the latest tag in the current branch, I am using a patched version of fpcupdeluxe which uses "git describe --tags" to generate the revision id. It is searching the current branch backwards until it finds a tag and then outputs the tag name and the number of commits on top of it. There is a tag named "main-2_3" placed somewhere in the main branch at the commit when the version number was bumped, so "main-2_3-321-g5ae19e4e" means 321 commits after the "main-2_3" tag.

The branch itself is actually called "main", its name just doesn't appear in the revision id.

So this bug report was made on the bleeding tip of the main branch.
« Last Edit: September 03, 2021, 07:05:08 pm by prof7bit »

JuhaManninen

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 3972
  • I like bugs.
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #87 on: September 04, 2021, 12:36:36 pm »
This is a showstopper, IMHO: https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/39347
Please test with the patch attached to the issue.
I have been busy with other tasks and not yet committed any code into the new official GitLab repo. I must recollect how to do it.
Mostly Lazarus trunk and FPC 3.2 on Manjaro Linux 64-bit.

prof7bit

  • Full Member
  • ***
  • Posts: 139
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #88 on: September 04, 2021, 01:53:03 pm »
Please test with the patch attached to the issue.
Changing build mode with:
  • main window toolbutton dropdown (fixed)
  • project inspector dropdown (fixed)
  • project settings combo box (still not working)
  • build modes manage dialog (still not working)

walkin-corpse

  • New Member
  • *
  • Posts: 10
Re: Lazarus Release Candidate 1 of 2.2.0
« Reply #89 on: September 05, 2021, 12:21:17 am »
Having plans to fix the wrong behavior of InstantFPC-apps in Windows?
If I start it tells "cannot find <path>\program1.exe". But there's only program1.pas and it running ok if started with "instantfpc program1.pas".
Is it bug or whatever?

 

TinyPortal © 2005-2018