Lazarus

Announcements => Lazarus => Topic started by: mattias on February 05, 2019, 12:13:56 pm

Title: Lazarus Release 2.0.0
Post by: mattias on February 05, 2019, 12:13:56 pm
The Lazarus team is glad to announce the release of Lazarus 2.0.0.

Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.4

Here is the list of fixes for Lazarus 2.0.x:
http://wiki.freepascal.org/Lazarus_2.0_fixes_branch

The release is available for download on SourceForge:
https://sourceforge.net/projects/lazarus/files/

Choose your CPU, OS, distro and then the "Lazarus 2.0.0" directory.

Checksums for the SourceForge files:
https://www.lazarus-ide.org/index.php?page=checksums#2_0_0

Minimum requirements:

Windows:
  2k, XP, Vista, 7, 8, 8.1 and 10, 32 or 64bit.

FreeBSD/Linux:
  gtk 2.8 for gtk2, qt4.5 for qt, qt5.6 for qt5, 32 or 64bit.

Mac OS X:
  10.5 to 10.12; Carbon (32bit), Cocoa (64bit, beta), qt and
  qt5 (32 or 64bit).

The svn tag is
https://svn.freepascal.org/svn/lazarus/tags/lazarus_2_0_0

For people who are blocked by SF, the Lazarus releases from SourceForge
are mirrored at: ftp://ftp.freepascal.org/pub/lazarus/releases/
and later at (after some time for synchronization)
http://mirrors.iwi.me/lazarus/
Title: Re: Lazarus Release 2.0.0
Post by: nouzi on February 05, 2019, 12:19:09 pm
 ;) thank lazaurs and freepascal  team 
Title: Re: Lazarus Release 2.0.0
Post by: Igor Kokarev on February 05, 2019, 01:06:06 pm
Thanks for your great work!
Title: Re: Lazarus Release 2.0.0
Post by: gerardus on February 05, 2019, 01:14:05 pm
Thank you for your excellent work!
Title: Re: Lazarus Release 2.0.0
Post by: Elfrom on February 05, 2019, 01:29:13 pm
Thanks for doing this great effort.
Lots of love goes out to Lazarus and FPC-team
Title: Re: Lazarus Release 2.0.0
Post by: UbuntuAccount on February 05, 2019, 02:09:52 pm
New Release of Delphi Compatible Professional RAD IDE;

- these are not very clear when including only LCL Components and using the brain on organizing the available commands to perform the customization of the presentation in logics of the Form Designer;
- which what would to expect on going out of this focus to understanding concepts of licenses which are not part of the workflow doing programming;
- resulting on unknown interests from the resulted EXE project[ and derivate Folder Files ] which how to proceed on understanding the concept of cease installation of Lazarus-IDE before going any further by presenting custom blogs and such for promoting the download of the compiled EXE file;

thanks;
Title: Re: Lazarus Release 2.0.0
Post by: howardpc on February 05, 2019, 02:38:26 pm
Great work Lazarus team! :)
I noticed on first use of a  vanilla 2.0.0 installation (Linux 64-bit) that the default key mapping had a built-in conflict with two key combinations allocated to Ctrl+Alt+O. A very minor oversight...
Title: Re: Lazarus Release 2.0.0
Post by: GetMem on February 05, 2019, 02:44:20 pm
Quote
I noticed on first use of a  vanilla 2.0.0 installation (Linux 64-bit) that the default key mapping had a built-in conflict with two key combinations allocated to Ctrl+Alt+O. A very minor oversight...
It's already fixed in Trunk. Unfortunately it was too late for 2.0.0.
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 05, 2019, 07:46:09 pm
WARNIG !!!! This Lazarus Release 2.0.0 is buggy !!!!

The code is running before the creation from all elements are finished !!!  %) :(

See pictures.
Title: Re: Lazarus Release 2.0.0
Post by: howardpc on February 05, 2019, 07:52:30 pm
I fail to see why you are attributing a SIGSEGV to LCL code rather than code you have written.
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 05, 2019, 07:57:49 pm
I start the EXE, and it close without error message.
This message is only showing with debugger, direct after start debug session, the form is not showing.

My code works good with Laz 1.8.4 an my code compile with 0 warnings (null, zero).
But with Laz 2.0.0, it crashes before the i can see the form.
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 05, 2019, 08:02:04 pm
The define from the variable is here:
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 05, 2019, 08:06:39 pm
Sorry, my code is a little bigger, only the main formular has 58655 code lines and the .lfm file has 52747 lines.

If my application works with a new lazarus, you can be sure, 99,999% is lazarus free from bugs. I'm the one from the million where can find out all what you need  >:D O:-)

PS: I have write this bug in the thread from RC3 - but it was ignored.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 05, 2019, 08:40:12 pm
The code is running before the creation from all elements are finished !!!  %) :(

If I get you right, then your code is in some event ( OnClick of some component?).
And you say that in 2.0.0 the event is fired while the form.create is still running, while in previous 1.8.4 it was not?

If that is the case, it is unfortunate this was not noticed with the release candidates... But anyway.

You should be able to
- provide a stacktrace
- provide a small example
  You should know the component, therefore be able to put it on a form, and be able to compare when the event is fired.
  In the example you may have to modify the same properties of that component (in OI) as you have done in your app. In case the event may depend on it.

With this data, you can then open a bugreport please.

EDIT:
just reading up:
Quote
PS: I have write this bug in the thread from RC3 - but it was ignored.
Sorry if it got missed. The anouncments get a lot of replies.

EDIT 2:
I found a reference to the German forum, that is the one you mean?
This is real unfortunate, the issue was even looked into. But somehow got lost somewhere. I still have the references what needs to be done.
Title: Re: Lazarus Release 2.0.0
Post by: Basile-B on February 05, 2019, 08:45:42 pm
Thanks to all the contributors for this nice release.
Title: Re: Lazarus Release 2.0.0
Post by: eny on February 05, 2019, 09:14:18 pm
Awesome  :)
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 05, 2019, 09:17:45 pm
1 -> Yes, OnClick Event.
2 -> Yes. In V1.8.4 this code was not fired while startup
3 -> StackTrace in picture
4 -> I make a small example, in ZIP
5 -> Bugreport done: https://bugs.freepascal.org/view.php?id=35018
Title: Re: Lazarus Release 2.0.0
Post by: ASBzone on February 05, 2019, 09:39:51 pm
Thanks to all the contributors for this nice release.

Indeed!  Thanks for all the hard work.
Title: Re: Lazarus Release 2.0.0
Post by: lucamar on February 05, 2019, 10:05:25 pm
At last! The actual 2.0 beta!  :P (just joking)

Well done, guys!
Title: Re: Lazarus Release 2.0.0
Post by: nachoap on February 05, 2019, 10:16:06 pm
Great, great, great news! Thank you very much. Lazarus is my favourite IDE for programming. Great!
Title: Re: Lazarus Release 2.0.0
Post by: jamie on February 05, 2019, 11:04:50 pm
@mmvisual

Looks like the TCheckBox is not testing for the state of the control  "csLoading" for example, before calling
the Onclick event.

 can you perform this same test in your OnClick handler to avoid this ? If it solves the issue then
maybe it can get fixed.

Title: Re: Lazarus Release 2.0.0
Post by: sstvmaster on February 05, 2019, 11:15:48 pm
@jamie

solved -> https://bugs.freepascal.org/view.php?id=35018
Title: Re: Lazarus Release 2.0.0
Post by: nachoap on February 05, 2019, 11:22:29 pm
Four apps perfectly compiled and working! Great!

https://ibb.co/DKQ4tk5 (https://ibb.co/DKQ4tk5)
https://ibb.co/hXdrg0Q (https://ibb.co/hXdrg0Q)
https://ibb.co/7QvsGwH (https://ibb.co/7QvsGwH)
https://ibb.co/YfBmHkJ (https://ibb.co/YfBmHkJ)

With Zeos, GR_32, BGRABITMAP, LazReport, SQLite, DcpCrypt...
Title: Re: Lazarus Release 2.0.0
Post by: lazaruzowski on February 05, 2019, 11:43:19 pm
Thank you to Lazarus team.
Title: Re: Lazarus Release 2.0.0
Post by: mmvisual on February 06, 2019, 12:12:23 am
The Bug is now fixed, thank you very much Michl.  :D
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 06, 2019, 06:42:49 am
Just to prove I read the release notes ....

A change of name for the DEB files  !

Previously, if you were lucky enough to have your (DEB Based) distro include FPC 3.0.4 you could use your package manager to install FPC and then pull down one of the SourceForge Lazarus deb files and install them.

However, we now see fpc as being two different beasts, the distro based fpc and the sourceforge fpc-laz. I don't know if its possible to install both (I really hope not!).

In a way, I see this change as a good thing, it now makes very clear choices between using your distro's packages or the (probably more current) SourceForge ones.

If you build Lazarus from source its still fine to use the fpc Ubuntu package repo and probably will be until the Laz developers decide to use a new FPC.

And I need to make some updates to my draft HowTo http://wiki.freepascal.org/Installing_Lazarus_on_Linux - but thats a good thing !

Davo
Title: Re: Lazarus Release 2.0.0
Post by: loaded on February 06, 2019, 08:13:43 am
Very thanks :)
Title: Re: Lazarus Release 2.0.0
Post by: m.abudrais on February 06, 2019, 09:05:03 am
Thank you for this great work :)
Title: Re: Lazarus Release 2.0.0
Post by: Deepaak on February 06, 2019, 09:22:19 am
Thank you Team Lazarus for this great work  ;D
Title: Re: Lazarus Release 2.0.0
Post by: mdalacu on February 06, 2019, 10:34:57 am
Great release!
But...i have tried to user pas2js package...
I have installed package weblaz supplied with the lazarus install.
i am unable to compile simpleserver.lpi :  TSimpleFileModule declaration is is missing form the file fpwebfile.pp
For you is is working?
Thx.

Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 06, 2019, 11:50:06 am
I feel a bit disingenuous to complain but it seems this bug https://bugs.freepascal.org/view.php?id=34795

did not get fixed before release ?  Its marked as 'resolved' and at r60064

It can crash a Linux app if an end user does what is a quite reasonable thing, attempt to paste an image into a TPicture.

Davo
Title: Re: Lazarus Release 2.0.0
Post by: Xor-el on February 06, 2019, 11:58:01 am
I feel a bit disingenuous to complain but it seems this bug https://bugs.freepascal.org/view.php?id=34795

did not get fixed before release ?  Its marked as 'resolved' and at r60064

It can crash a Linux app if an end user does what is a quite reasonable thing, attempt to paste an image into a TPicture.

Davo

Unfortunately, it seems the change didn't make it to 2.0.0 release.
The best option is to use the fixes branch or trunk to compile your release.
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 06, 2019, 12:03:49 pm
......
The best option is to use the fixes branch or trunk to compile your release.
Oh, its dead easy to apply the patch to my source tree but its one of those "know issues" we'd all prefer not to see in a release.....

Davo
Title: Re: Lazarus Release 2.0.0
Post by: Xor-el on February 06, 2019, 12:13:25 pm
......
The best option is to use the fixes branch or trunk to compile your release.
Oh, its dead easy to apply the patch to my source tree but its one of those "know issues" we'd all prefer not to see in a release.....

Davo

I understand but unfortunately some fixes didn't make it to the current major release probably because of time constraints.
Title: Re: Lazarus Release 2.0.0
Post by: Ondrej Pokorny on February 06, 2019, 02:13:28 pm
......
The best option is to use the fixes branch or trunk to compile your release.
Oh, its dead easy to apply the patch to my source tree but its one of those "know issues" we'd all prefer not to see in a release.....

Why didn't you complain before the 2.0.0 release? You have had 1 month time to do so. You can always check what fixes are applied into the fixes branch in the SVN or http://wiki.freepascal.org/Lazarus_2.0_fixes_branch (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch).
Title: Re: Lazarus Release 2.0.0
Post by: Thaddy on February 06, 2019, 03:45:44 pm
Why didn't you complain before the 2.0.0 release? You have had 1 month time to do so. You can always check what fixes are applied into the fixes branch in the SVN or http://wiki.freepascal.org/Lazarus_2.0_fixes_branch (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch).
Indeed. You had ample time to test and report.

To the team: great release.
Title: Re: Lazarus Release 2.0.0
Post by: nachoap on February 06, 2019, 05:04:02 pm
Is Zeosdb 7.2.4 working well with Lazarus 2.0? I can see all data and I can insert new rows. Everything is allright but when I close my app all new data is lost :O and I have got a db file not updated :(
Title: Re: Lazarus Release 2.0.0
Post by: af0815 on February 06, 2019, 06:19:56 pm
Is Zeosdb 7.2.4 working well with Lazarus 2.0? I can see all data and I can insert new rows. Everything is allright but when I close my app all new data is lost :O and I have got a db file not updated :(
ApplyUpdates used ? http://zeoslib.sourceforge.net/viewtopic.php?t=3797
Title: Re: Lazarus Release 2.0.0
Post by: MarkZ on February 06, 2019, 06:25:03 pm
Thanks for the release. A few installation issues appeared.

I did a side-by-side 32-bit install to 1.8.4 on Win10-64, so got the dialog for config file version conflict and to use the --pcp option for having 2 installs, which I did using the Windows-R Run dialog. After doing this Laz2 does not remember this was set on the previous run and to use the new config directory when it starts. I had to manually edit the startup shortcut to use the option on each invoke.

Also, it would be nice if the installer asked which top menu name/shortcut name prefix should be used when a previous installation is detected but not being upgraded and overwritten, so the shortcuts and menus from existing version aren't affected.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 06, 2019, 07:13:23 pm
I did a side-by-side 32-bit install to 1.8.4 on Win10-64, so got the dialog for config file version conflict and to use the --pcp option for having 2 installs, which I did using the Windows-R Run dialog. After doing this Laz2 does not remember this was set on the previous run and to use the new config directory when it starts. I had to manually edit the startup shortcut to use the option on each invoke.

Also, it would be nice if the installer asked which top menu name/shortcut name prefix should be used when a previous installation is detected but not being upgraded and overwritten, so the shortcuts and menus from existing version aren't affected.

The installer really only supports shortcuts/menu for one install, since (afaik) all shortcuts have the same name. (Of course once you renamend them, it should be fine.

You should NOT need to edit the properties of the shortcut(s) to add pcp.

If you click on "secondary install" you will be ask for a config dir. This config dir is stored inside the lazarus dir, in a file called lazarus.cfg.
Title: Re: Lazarus Release 2.0.0
Post by: nachoap on February 06, 2019, 08:12:17 pm
Is Zeosdb 7.2.4 working well with Lazarus 2.0? I can see all data and I can insert new rows. Everything is allright but when I close my app all new data is lost :O and I have got a db file not updated :(
ApplyUpdates used ? http://zeoslib.sourceforge.net/viewtopic.php?t=3797

Solved: Autocommit property in TZConnection was False. But is has been working for 2 years with previous Lazarus and Zeos 7.1.4 and older :O
Title: Re: Lazarus Release 2.0.0
Post by: nouzi on February 06, 2019, 08:18:28 pm
Is Zeosdb 7.2.4 working well with Lazarus 2.0? I can see all data and I can insert new rows. Everything is allright but when I close my app all new data is lost :O and I have got a db file not updated :(
AutoCommit = true
Title: Re: Lazarus Release 2.0.0
Post by: BSaidus on February 06, 2019, 08:31:43 pm
 ::) ::) ::)
Thanks you Lazarus/Fpc team for great work.
You are men !!
Title: Re: Lazarus Release 2.0.0
Post by: jwdietrich on February 06, 2019, 09:20:20 pm
Thanks to the team and all contributors for your ingenious work! Lazarus 2.0 is the best ever! The maturation is especially evident with macOS.
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 06, 2019, 11:19:33 pm
https://bugs.freepascal.org/view.php?id=34795
Why didn't you complain before the 2.0.0 release? You have had 1 month time to do so. You can always check what fixes are applied into the fixes branch in the SVN or http://wiki.freepascal.org/Lazarus_2.0_fixes_branch (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch).
Thaddy :
Indeed. You had ample time to test and report.
In case thats a genuine question -
1. It was marked as resolved and applied  in the bug tracker, I thought that enough to be sure it was 'happening'.
2. My only previous experience with releases was 1.8.4, there were 5 release candidates there. And there were statements to the effect, test now ...

I was aware it was not fixed in RC3, I do test the release candidates and I do report problems when I see them. But endless nagging is not welcome nor productive.

I might add I have no particular interest in this bug, my project does not do any images. I came across it, reported it, helped track it down. And now mention that its present in 2.0.0 and might affect someone else. And for that I blamed ! OK.

Davo
 
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 07, 2019, 12:26:46 am
2. My only previous experience with releases was 1.8.4, there were 5 release candidates there. And there were statements to the effect, test now ...

Maybe we need to work on how/that we communicate release candidate schedules.

Also at the moment there is little extra organization how regressions are handled. That is everyone is committed to fix them of course. But there is no central checking point to ensure all known regression are fixed (as far as possible).

The RCs are announced. Bug reports and regression reports are mixed with other postings here on the forum. A few are posted on the mail list. Some are reported on mantis, but they are not marked there as regressions. So they occasionally get lost.

Need to see what can be done.
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 07, 2019, 12:38:02 am
Thanks Martin for your well considered words.

Should that particular bug be "re-logged" or reopened or what to ensure it is deal with in later releases ?

Davo
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 07, 2019, 01:03:23 am
Excellent news! Many thanks to the team.

I will begin installing it on my machines.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 07, 2019, 01:23:07 am
Should that particular bug be "re-logged" or reopened or what to ensure it is deal with in later releases ?
I am getting feedback, if it was an oversight, or if there were other reasons. (I can't comment on the issue myself, not my area)

For reference, if an issue will be (or has been) merged can be seen here: http://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch
(Extremely rarely someone may merge something without putting it on the list, then only svn logs will tell..., but realy that is extremely rare.)

Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 07, 2019, 02:16:19 am
For reference, if an issue will be (or has been) merged can be seen here: http://wiki.lazarus.freepascal.org/Lazarus_2.0_fixes_branch
Ah, very useful indeed. I'll book mark that and watch for the bug, if it does not show up, I'll yell out !

And I do think it would be useful to announcement formal release is imminent, something along the lines of "RC3 is looking like it folks." Just "process improvement", not a complaint. Given the fabulous job done by a bunch of volunteers, I'm not silly enough to complain !

Thanks.
Davo
Title: Re: Lazarus Release 2.0.0
Post by: avk on February 07, 2019, 08:17:54 am
Congratulations to the Lazarus team!
Title: Re: Lazarus Release 2.0.0
Post by: bobkos on February 07, 2019, 02:57:33 pm
So first of all thank you to all contributors for next release!

May I ask a question just fro my understanding, I have some calcaulator form in my application and of course I'm handling "division by zero" cases by "try except" section, however after update to 2.0 I've found that instead of "exceptions" it's become assigning a "+Inf" as value. After some investigation I've found a thread on forum about explanation and tip how to deal it by excluding TFPUExceptionMask's option - exZeroDivide. My question is, if it really old behavior of FPC/Lazarus why that's was not happened before in Lazarus 1.8.2 on the same PC?

Thank you in advance.
Title: Re: Lazarus Release 2.0.0
Post by: MarkZ on February 07, 2019, 08:51:55 pm
I did a side-by-side 32-bit install to 1.8.4 on Win10-64, so got the dialog for config file version conflict and to use the --pcp option for having 2 installs, which I did using the Windows-R Run dialog. After doing this Laz2 does not remember this was set on the previous run and to use the new config directory when it starts. I had to manually edit the startup shortcut to use the option on each invoke.

Also, it would be nice if the installer asked which top menu name/shortcut name prefix should be used when a previous installation is detected but not being upgraded and overwritten, so the shortcuts and menus from existing version aren't affected.

The installer really only supports shortcuts/menu for one install, since (afaik) all shortcuts have the same name. (Of course once you renamend them, it should be fine.

You should NOT need to edit the properties of the shortcut(s) to add pcp.

If you click on "secondary install" you will be ask for a config dir. This config dir is stored inside the lazarus dir, in a file called lazarus.cfg.

Secondary install applies to same version numbers, i.e. 2.0 release and 2.0 fixes; installer was complaining "base version not found" or some such when I tried that option. This "lazarus.cfg" file is not mentioned as what is checked for in addition to the default dir, or its format if someone wants create or edit it manually, that I've seen in the docs. The --pcp option doesn't create it either, apparently only the installer does. It also does not have a location entry in Options/Environment/Files dialog pane, so side-by-sides of the same version can share a config file if they want, for this .cfg or the config file itself directly.

Yes, the menu shortcuts can have the same name, if the menu directory they're part of is named differently. I think (haven't looked at them in detail recently) menu directory name is static strings in .ist files, not variables like install dir. Desktop shortcuts could be handled similarly, afaik.

Given for fresh installs these gotchas don't apply these comments are nits, not bug reports, but would enhance the OOBE for other users of the current version, I imagine, that like me want to test things in the new one for unknown regressions with their own code.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 07, 2019, 09:46:30 pm
I replied in a new thread: http://forum.lazarus-ide.org/index.php/topic,44197
Title: Re: Lazarus Release 2.0.0
Post by: JuhaManninen on February 08, 2019, 07:53:52 am
I feel a bit disingenuous to complain but it seems this bug https://bugs.freepascal.org/view.php?id=34795
did not get fixed before release ?  Its marked as 'resolved' and at r60064
I marked it now for merging to fixes branch and thus 2.0.2.
I guess I wanted more testing for it and then forgot it.
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 08, 2019, 01:16:01 pm
I marked it now for merging to fixes branch and thus 2.0.2.
Thanks Juha, I'll watch for it to appear this time!

Davo
Title: Re: Lazarus Release 2.0.0
Post by: piola on February 08, 2019, 01:35:02 pm
It was marked as resolved and applied  in the bug tracker, I thought that enough to be sure it was 'happening'.

Obviously the same thing happened to a bug (https://bugs.freepascal.org/view.php?id=34545) that I reported. It's even mentioned that it's fixed ("r59951 IDE") (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch), but it ain't.

This is a very annoying issue because you have to confirm the warning on each and every compile. Hope it's scheduled for 2.2 now.
Title: Re: Lazarus Release 2.0.0
Post by: JuhaManninen on February 08, 2019, 02:51:03 pm
Obviously the same thing happened to a bug (https://bugs.freepascal.org/view.php?id=34545) that I reported. It's even mentioned that it's fixed ("r59951 IDE") (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch), but it ain't.
Did you check from the commit log and it is not merged? Does it work for you in trunk?

Quote
This is a very annoying issue because you have to confirm the warning on each and every compile. Hope it's scheduled for 2.2 now.
If it really is missing, it will be merged for 2.0.2.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 08, 2019, 04:11:46 pm
It was marked as resolved and applied  in the bug tracker, I thought that enough to be sure it was 'happening'.

Obviously the same thing happened to a bug (https://bugs.freepascal.org/view.php?id=34545) that I reported. It's even mentioned that it's fixed ("r59951 IDE") (http://wiki.freepascal.org/Lazarus_2.0_fixes_branch), but it ain't.
I just tested with fixes 2.0 (which is the same as release + 2 lldb fixes, so for this issue: the same)
- New project (empty form), saved D:\project.lpi/lpr D:\unit1.pas, compiled, run.

I can not reproduce it (and I did get the issue in Dec 2018).

I also found the entry on the merge wiki, search for r59952 => that is the revision resulting from the merge.
Since it is fixed (or at least a fix committed) to trunk and fixes branch, there are 2 commits. r59951 and r59952

It is unfortunate that the one mentioned in mantis and the wiki differ...., but that is a 2ndary problem. (and searching for the issue number 34545 will find it)
If you indeed still get it on release 2.0.0 then we need new steps to reproduce.
Title: Re: Lazarus Release 2.0.0
Post by: piola on February 08, 2019, 04:20:35 pm
- New project (empty form), saved D:\project.lpi/lpr D:\unit1.pas, compiled, run.

I can not reproduce it (and I did get the issue in Dec 2018).

Quite funny  :) when I do the same, it works fine for me too.

Try this:

- New project, empty form
- Save both to d:\temp
- In project options, set target filename to D:\project1.exe
- Compile -> Warning about missing output directory (at least for me  ;))
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 08, 2019, 05:10:19 pm
Yes then it happens. Working on it.
Title: Re: Lazarus Release 2.0.0
Post by: piola on February 08, 2019, 08:00:21 pm
In 2.0, I am observing severe problems when debugging. Is there someone else having problems?

My setup is Win x64, using Lazarus x64, cross-compiling to Win32.

In the 2.0 release, the "evaluate/watch" windows (as well as the tooltip when hovering over a variable) shows only rubbish data for strings. Records are displayed as "no symbol in current context". Only very basic types (integer, float) seem to be ok. This hasn't occured in the release candidates. (I already tried various dwarf2/dwarf3 settings, but without success.)

In addition to that, the debugger crashes very frequently. It is enough to have a single breakpoint at which the program execution is paused and then removing that breakpoint. Setting or removing breakpoints while the program is running is a no-go and almost always crashes the debugger. These problems have occured only rarely in 1.8, but were already present in the 2.0 release candidates.

Is there something more I can try?
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 08, 2019, 09:55:34 pm
In 2.0, I am observing severe problems when debugging. Is there someone else having problems?

My setup is Win x64, using Lazarus x64, cross-compiling to Win32.

In the 2.0 release, the "evaluate/watch" windows (as well as the tooltip when hovering over a variable) shows only rubbish data for strings. Records are displayed as "no symbol in current context". Only very basic types (integer, float) seem to be ok. This hasn't occured in the release candidates. (I already tried various dwarf2/dwarf3 settings, but without success.)

In addition to that, the debugger crashes very frequently. It is enough to have a single breakpoint at which the program execution is paused and then removing that breakpoint. Setting or removing breakpoints while the program is running is a no-go and almost always crashes the debugger. These problems have occured only rarely in 1.8, but were already present in the 2.0 release candidates.

Is there something more I can try?
I can't think of any change that would have introduced this. Not on the gdb based debugger.


It would be good if you can get a log of some of the errors.
http://wiki.lazarus.freepascal.org/GDB_Debugger_Tips#Log_info_for_debug_session

If watches/locals are botched, you can also open the history window, and export the history. This will allow me to see the watches in my IDE, as you had seen them in yours.

Both, log and history, contain data from your app. In case you have sensitive data, we can discuss sending them privately.

A short sample code may also help.

Also do problems (for each case of problem) apply to:
global var
fields of self
class fields of other classes: foo.somestring
local vars
local vars but accessed from a nested procedure
params
var params

You do not need to test them all, just specify for those that fail in your code.




You can try to use alternative gdb versions.
For 32 bit (including cross compiled to 32 bits) https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits/Alternative%20GDB/

You can also try to make sure that packages, if they have debug info, use the same type as your project.
GDB's stabs support is declining. But fpc on win32 still defaults to that. And if you change your project settings, packages may still use stabs, and that can be an issue.
Either edit Tools > Configure build IDE: and add -gw for dwarf
Or go to additions and overrides, and create an entry for all package, except project (IIRC *,-#project or similar, search our wiki) and set it to -gw or to -g- if you need no debug info for packages.
Title: Re: Lazarus Release 2.0.0
Post by: LPCVOID on February 09, 2019, 05:23:57 pm
Thanks a lot, great work guys!
Title: Re: Lazarus Release 2.0.0
Post by: Soob on February 09, 2019, 05:49:06 pm
I downloaded the new version and I keep getting an error that the file graphtype.pp hasn't been found. On other PC I get message that the file lmessaage.pp is not found. I found them on the internet but the program won't run either.

Does anybody have the same problem? I'm using 64-bit version of Windows 10.

Edit: // I've attached the error so you can see it. Maybe it'll help
Title: Re: Lazarus Release 2.0.0
Post by: m.abudrais on February 09, 2019, 06:20:53 pm
you have incompatible ppu , i thank that means the file is compiled with different fpc version.
what is the previous  version of lazarus that you installed?
i suggest rebuilding lazarus ide,
or uninstall lazarus and deleting all content of the folder C:\lazarus and then install it again.
Title: Re: Lazarus Release 2.0.0
Post by: JuhaManninen on February 09, 2019, 06:43:50 pm
Soob, you have leftover units from an old installation.
You must uninstall the old one before installing a new major version. Minor dot release update may succeed without it.
Title: Re: Lazarus Release 2.0.0
Post by: Soob on February 09, 2019, 06:48:10 pm
Yes, I re-installed Lazarus and it works perfectly now :) thank you
Title: Re: Lazarus Release 2.0.0
Post by: hillfolk on February 10, 2019, 02:53:43 pm
 :) Thank you for Lazarus Team
Title: Re: Lazarus Release 2.0.0
Post by: scribly on February 10, 2019, 05:35:39 pm
After some cleanup and only minor adjustments here and there I managed to compile my project(CE) without any issues, and everything seems to be looking fine so far.  No flashing listviews, no instant crashes, po files that don't start with hundreds KB of random garbage

So well done. I'll have to do some testing but I might finally be able to move from 1.6.4 with custom patches to an official build again
(Still have to launch lazarus itself with DPI disabled because it does 'something' to the existing controls when loading a project designed on 96 dpi)

Still hoping to see FPC updated someday as well
Code: [Select]
Fatal: (1018) Compilation aborted
An unhandled exception occurred at $0000000100021F3D:
EListError: List index exceeds bounds (1)
  $0000000100021F3D
  $000000010016712B
  $0000000100167A36
  $00000001001675B3
  $0000000100167832
  $000000010016712B
  $0000000100167A36
  $00000001001675B3
  $0000000100167832
  $000000010016712B
  $0000000100167A36
  $00000001001675B3
  $0000000100167832
  $000000010016712B
  $0000000100167A36
  $00000001001675B3
  $0000000100167832

Error: C:\lazarus200\fpc\3.0.4\bin\x86_64-win64\ppcx64.exe returned an error exitcode
(I heard it was already fixed several years ago, but hasn't made it to the fpc version used here)
Title: Re: Lazarus Release 2.0.0
Post by: jamie on February 10, 2019, 06:45:54 pm
I just installed the 32 bit version on my W2k machine, it works perfectly!  :D

Thank you men!
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 11, 2019, 02:58:24 am
I just installed 2.0.0 Mac and can not run a default program to display a form. Nothing displays, and I can not stop the program, so am forced to to do a hard quit. I installed it in a clean directory.

lazarus-2.0.0-i686-macosx.dmg

The 2.0.0 (now 2.0.1) fixes on svn was running fine.

Anyone having better luck?
Title: Re: Lazarus Release 2.0.0
Post by: BeanzMaster on February 11, 2019, 01:46:36 pm
Hi, just downloaded Lazarus 2.0 for windows
Impossible to install Zeos DB components missing ZComponent. Impossible to install SQLite component since have the DLL in system folder  :'(

Have you plane to make an installer for macos 64bits with QT, or do you plane to make one, only when Cocoa will be stable ?

Cheers good work ! ;)
Title: Re: Lazarus Release 2.0.0
Post by: Zoran on February 11, 2019, 02:51:51 pm
Hi, just downloaded Lazarus 2.0 for windows
Impossible to install Zeos DB components missing ZComponent. Impossible to install SQLite component since have the DLL in system folder  :'(

Have you plane to make an installer for macos 64bits with QT, or do you plane to make one, only when Cocoa will be stable ?

Cheers good work ! ;)

There must be some specific problem in your system. I have no problem with Zeos installation in Windows 8 and 10, and Linux (mint xfce, 18.3, 19.1).

I don't use SQLite, so I have no idea about it.

How did you install Zeos? Maybe some locations are messed up from previous install. Try this:

1. First, make sure zeos is not installed (in main menu go to Package->Install/Uninstall packages and make sure to remove all five zeos packages -- that is zcore, zplain, zdbc, zparsesql and zcomponent).
2. Make Lazarus "forget" these packages (go to Package->Package links and search for zeos, then check all five zeos packages and click on "Delete selected" button). You might see more than five links there (if you tried different version of Zeos) -- that will make problem, IDE might mix packages with different versions -- just remove them all here.
3. Rebuild the IDE.
4. Go to Package->Open package file. Open five zeos packages from the same directory in the ide. In the zcomponent window click on install button and rebuild Lazarus again.

Did it help?
Title: Re: Lazarus Release 2.0.0
Post by: avra on February 11, 2019, 03:09:07 pm
Impossible to install SQLite component since have the DLL in system folder  :'(
Put sqlite3.dll of propper bitness into directory of your Lazarus executable.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 11, 2019, 03:18:50 pm
I just installed 2.0.0 Mac and can not run a default program to display a form. Nothing displays, and I can not stop the program, so am forced to to do a hard quit. I installed it in a clean directory.
No idea, not using Mac myself.

But, what happens if you
- start the program: run without debug
- compile it, start it outside the IDE
?
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 11, 2019, 04:19:48 pm
No idea, not using Mac myself.

But, what happens if you
- start the program: run without debug
- compile it, start it outside the IDE
?

Thanks Martin. It did work without debugging. When I checked to make sure I was using the new debugger, I realized the path defaults to gdb, even though lldb is selected. I changed the path to point to lldb (/usr/bin/lldb) and everything seems fine now.

The path to lldb is not available in the combobox either. Since Mac hides system directories, it is difficult to navigate to it, as you can not pick it from the normal open file dialog. I installed a command to toggle on and off hidden directories, but this would not likely be obvious to a new user. It is still much easier than dealing with codesigning gdb though!  :)
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 11, 2019, 04:47:51 pm
The path to lldb is not available in the combobox either. Since Mac hides system directories, it is difficult to navigate to it, as you can not pick it from the normal open file dialog. I installed a command to toggle on and off hidden directories, but this would not likely be obvious to a new user. It is still much easier than dealing with codesigning gdb though!  :)

There are several issues

1) the path. I added a commit to trunk, that will hopefully add it. (will merge)
But that will not automatically select it.

2) The setup dialog "lazarus --setup" does not know at all about lldb.
There is no imminent work planed on this, that I know of....

3) A new install, without old config.
That should work...
But then it should have worked with your config from the RC, unless the RC had a diff config folder.

Upgrading with existing config from 1.8.4 => that does not update the debugger conf.


Could you test:
If you  (in your primary config), rename the environmentoptions.xml
Then start the IDE. It should create a new environmentoptions.xml, and the debugger should be correct.

Also verify, in your install directory, is a environmentoptions.xml which is the template for a new config. That should have the lldb debugger in it.
Title: Re: Lazarus Release 2.0.0
Post by: BeanzMaster on February 12, 2019, 09:58:02 am

There must be some specific problem in your system. I have no problem with Zeos installation in Windows 8 and 10, and Linux (mint xfce, 18.3, 19.1).

How did you install Zeos?


I have just installed a fresh lazarus 2.0 as secondary (i want to keep and old version for other purpose) so none package or other already installed.
For Zeos is available in "official" list in menu->Package-Install/Remove packages so i've just added it to the list ( see screenshot)

Put sqlite3.dll of propper bitness into directory of your Lazarus executable.
I say that but no project open. Like i said before it's fresh installation. So when i rebuild IDE i have en error message like "SQLite.DLL not found"

See also screenshot i've surrounded the packages

This two errors are not  realy a problem for zeos  i'try thrue OPM and for SQLite i'll just try to put DLL in my system's folders

Thanks
Title: Re: Lazarus Release 2.0.0
Post by: avra on February 12, 2019, 10:16:49 am
Put sqlite3.dll of propper bitness into directory of your Lazarus executable.
I say that but no project open. Like i said before it's fresh installation. So when i rebuild IDE i have en error message like "SQLite.DLL not found"
So, you think that without sqlite3.dll IDE will somehow magically know how to access SQLite? Good for you...  %)
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 12, 2019, 11:18:48 am
The nature of the "Terminal Output" - (View->DebugWindows->TerminalOutput) in 1.8.4 and (View->DebugWindows->ConsoleInOutput) in 2.0.1 has changed. I note two issues on Linux -

1. Crash if you close the Console window before closing an app.

2. In my medium sized app, I debugln() no longer writes to the Console.

Specifically, if I make a new project, it can use debugln() to write to the console but my medium sized project that has been brought forward from 1.8.4 and then various versions of Fixes_2 and now V2.0.0 cannot. I am pretty sure there was no problem in older Fixes_2 - I'd have noticed.

I have read the 2.0.0 release notes, it talks about LCL no longer writing out over Lazlogger, but I have Lazlogger listed in my units uses clause.

Item 1 - crashes if you close the console winder before the app ?  Simple form with a button, in the event for that button  put debugln('hello'); and add Lazlogger to users line.

Now, run the app in Lazarus, open the Console (View->DebugWindows->ConsoleInOutput), press the button in your app, note it does say Hello (unlike my older app) and then close the console window. Bang.

I really liked the old Terminal window approach, any way I can get it back ?

Davo
Title: Re: Lazarus Release 2.0.0
Post by: OdyssseusL on February 12, 2019, 12:59:22 pm
I see, that the macOS version 2.0.0 is build with "carbon". Does there exist a version with "Cocoa"?

Thanks in advance.
Title: Re: Lazarus Release 2.0.0
Post by: Thaddy on February 12, 2019, 01:20:14 pm
You can build it yourself by selecting the widgetset when compiling Lazarus,
As it stands I am just as flabbergasted as you that the distribution is build with carbon.
That's silly. It can't possibly last longer than this version because 32 bit got dropped.
It should have been addressed already.
Title: Re: Lazarus Release 2.0.0
Post by: BeanzMaster on February 12, 2019, 03:11:58 pm
Put sqlite3.dll of propper bitness into directory of your Lazarus executable.
I say that but no project open. Like i said before it's fresh installation. So when i rebuild IDE i have en error message like "SQLite.DLL not found"[/quote]
So, you think that without sqlite3.dll IDE will somehow magically know how to access SQLite? Good for you...  %)
[/quote]

Sorry for my english,
In this case the best it's to copy the DLL in the system folder and not in the Lazarus folder. Because with a project we should copy also the DLL in the application folder.

In this case it's how the components in those 2 packages are coded. I don't take a look in the code but Normally we should not need to load the DLL when installing these components in the IDE because we do not connect to any database.

To do it well it would be necessary that the DLL is loaded dynamically during the execution of our project or when we let's enable a connection with a BDD at designtime.

When installing a package of components of this type we can not rebuild Lazarus. Making two copies of a DLL file is stupid, in which case it is better to copy this DLL to the system folder of the OS and not to the Lazarus folder and then to copy it a second time to the application's folder.

In some of my projects i'm using OpenAL/Freetype and others. I have some components installed in the IDE and i don't need to have the DLL in the Lazarus's folder or in the system's folder. I just put DLL in my application's folder and DLL is load at dynamically at runtime and that it.

I think this minimum information should be to register in the description of the package.
This kind of error does not bother me more than that but for someone who starts it can become frustrating.

In all case it's not a problem for me
Title: Re: Lazarus Release 2.0.0
Post by: garlar27 on February 12, 2019, 03:36:38 pm
BeanzMaster,
In this case it's how the components in those 2 packages are coded. I don't take a look in the code but Normally we should not need to load the DLL when installing these components in the IDE because we do not connect to any database.

To do it well it would be necessary that the DLL is loaded dynamically during the execution of our project or when we let's enable a connection with a BDD at designtime.

When installing a package of components of this type we can not rebuild Lazarus. Making two copies of a DLL file is stupid, in which case it is better to copy this DLL to the system folder of the OS and not to the Lazarus folder and then to copy it a second time to the application's folder.

In some of my projects i'm using OpenAL/Freetype and others. I have some components installed in the IDE and i don't need to have the DLL in the Lazarus's folder or in the system's folder. I just put DLL in my application's folder and DLL is load at dynamically at runtime and that it.

The IDE needs the DLL because you can open a see the DB data at design time.

On windows the library "bitness" is a pain in the butt (the system folders don't seem to have the right name) I suppose that's why they tell you "copy the dll here and there" so if you know the right place for the sqlite3.dll then put it there.
Title: Re: Lazarus Release 2.0.0
Post by: Martin_fr on February 12, 2019, 06:14:49 pm
The nature of the "Terminal Output" - (View->DebugWindows->TerminalOutput) in 1.8.4 and (View->DebugWindows->ConsoleInOutput) in 2.0.1 has changed. I note two issues on Linux -

1. Crash if you close the Console window before closing an app.

I really liked the old Terminal window approach, any way I can get it back ?
Please report on mantis.

Make a separate mantis feature request, for which changes in the debug output you would like an option.

Quote
2. In my medium sized app, I debugln() no longer writes to the Console.

Specifically, if I make a new project, it can use debugln() to write to the console but my medium sized project that has been brought forward from 1.8.4 and then various versions of Fixes_2 and now V2.0.0 cannot. I am pretty sure there was no problem in older Fixes_2 - I'd have noticed.

I have read the 2.0.0 release notes, it talks about LCL no longer writing out over Lazlogger, but I have Lazlogger listed in my units uses clause.

Strange if you have LazLogger in the uses, then it is supposed to work.

Do you use threads? Make sure the main thread gets the first debugln. That problem always existed, and afaik is the same for writeln.
Btw: does writeln work?

Have you tried running your app from a console (cmd.exe on windows, bash or terminal on linux)

Can you debug how the code steps into debugln? It must abort at some condition.
Title: Re: Lazarus Release 2.0.0
Post by: segfault on February 12, 2019, 06:17:59 pm
I haven't installed it yet, just wondering whether pas2js is now integrated with it? And if so does it work?  :D
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 12, 2019, 06:38:31 pm

There are several issues

1) the path. I added a commit to trunk, that will hopefully add it. (will merge)
But that will not automatically select it.

2) The setup dialog "lazarus --setup" does not know at all about lldb.
There is no imminent work planed on this, that I know of....

3) A new install, without old config.
That should work...
But then it should have worked with your config from the RC, unless the RC had a diff config folder.

Upgrading with existing config from 1.8.4 => that does not update the debugger conf.


Could you test:
If you  (in your primary config), rename the environmentoptions.xml
Then start the IDE. It should create a new environmentoptions.xml, and the debugger should be correct.

Also verify, in your install directory, is a environmentoptions.xml which is the template for a new config. That should have the lldb debugger in it.

I did upgrade from 1.8.4, so that likely caused the problem. While I removed the install directory, I did not remove the config directory. After renaming environmentoptions.xml and restarting the IDE, the correct lldb path does appear, and lldb works.

I could not find the template in the install directory however.

Thanks.

 
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 12, 2019, 06:50:25 pm
You can build it yourself by selecting the widgetset when compiling Lazarus,
As it stands I am just as flabbergasted as you that the distribution is build with carbon.
That's silly. It can't possibly last longer than this version because 32 bit got dropped.
It should have been addressed already.

Yes, that is a problem for me. I may stick with the 2.0 fixes branch on Mac for a while yet. The cocoa IDE still has some problems, like not being able to delete controls in the form editor, and contextual menus not working, but is generally in good shape. I posted bug reports, and hope these issues will get addressed in fixes.
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 13, 2019, 10:19:46 am
1. Crash if you close the Console window before closing an app.
Please report on mantis.

Have done so, https://bugs.freepascal.org/view.php?id=35071
Quote
2. In my medium sized app,  debugln() no longer writes to the Console.
Strange if you have LazLogger in the uses, then it is supposed to work.

EDIT: Ahh, how embarrassing - I had a --debug-log=<file> set in run parameters !  Sorry for the noise, disregard all about not seeing debugln output.

The problem with crash if closing console window before app still exists...

Davo
Title: Re: Lazarus Release 2.0.0
Post by: Zoran on February 14, 2019, 01:31:04 pm
There is regression with TStringGrid.OnUserCheckboxBitmap - no checkboxes are shown at all, just blank cells.

I tracked down that bug was introduced in trunk last spring.
I created the bugreport, there I gave more details (test application, screenshots, revisions which introduced the bug): https://bugs.freepascal.org/view.php?id=35085 (https://bugs.freepascal.org/view.php?id=35085)
Title: Re: Lazarus Release 2.0.0
Post by: PierceNg on February 14, 2019, 02:40:24 pm
I just installed 2.0.0 Mac

lazarus-2.0.0-i686-macosx.dmg

How do you install it?

I'm running Mojave. I downloaded following from SF:
- fpc-3.0.4.intel-macosx.dmg
- fpc-src-3.0.4-macosx.dmg
- lazarus-2.0.0-i686-macosx.dmg

When attempting to install fpc-3.0.4-intel-macosx, I get attached error. I have Xcode and command line tools installed.

SOLVED: Nevermind, I missed the step about installing the SDK headers as per the wiki page. Now installed.
Title: Re: Lazarus Release 2.0.0
Post by: VTwin on February 14, 2019, 07:58:15 pm
SOLVED: Nevermind, I missed the step about installing the SDK headers as per the wiki page. Now installed.

Excellent! Yes, it can be confusing, but the wiki is helpful. Luckily the new debugger makes things much easier than using gdb. I look forward to the complete transition to cocoa.
Title: Re: Lazarus Release 2.0.0
Post by: istoica on February 15, 2019, 03:30:49 pm
Wow, this is so great! Congratulations on all levels!

Will you guys be able to provide a more convenient way to switch to SDI interface ?

I mean, I am using it daily on OSX, Xubuntu and Windows, I found no issues so far, unless I am installing the wrong packages or the wrong order.

On Windows, there is still the problem of not finding sqlite3.dll file when activating some packages, couldn't this be solved too ?
Title: Re: Lazarus Release 2.0.0
Post by: Zoran on February 15, 2019, 04:24:29 pm
There is regression with TStringGrid.OnUserCheckboxBitmap - no checkboxes are shown at all, just blank cells.

I tracked down that bug was introduced in trunk last spring.
I created the bugreport, there I gave more details (test application, screenshots, revisions which introduced the bug): https://bugs.freepascal.org/view.php?id=35085 (https://bugs.freepascal.org/view.php?id=35085)

This event should have never been used the way I used it, so I resolved the bug with "no change required". More details in bugreport.
Title: Re: Lazarus Release 2.0.0
Post by: JanRoza on February 15, 2019, 07:14:26 pm
Wow, this is so great! Congratulations on all levels!

Will you guys be able to provide a more convenient way to switch to SDI interface ?

I mean, I am using it daily on OSX, Xubuntu and Windows, I found no issues so far, unless I am installing the wrong packages or the wrong order.

On Windows, there is still the problem of not finding sqlite3.dll file when activating some packages, couldn't this be solved too ?

Have you copied the sqlite3.dll to the main Lazarus folder?
With the dll in the Lazarus folder I have never had any package complaining during installation.
Title: Re: Lazarus Release 2.0.0
Post by: garlar27 on February 15, 2019, 10:44:34 pm
The other way is to put the SQLite.dll in the correct System folder (System or SysWOW64).
Title: Re: Lazarus Release 2.0.0
Post by: carondaniel1957 on February 16, 2019, 02:02:36 pm
Good day to all
Using Linux Ubuntu 18.10, Lazarus 18.4 installed, I am trying to install the new version but when I double-click the downloaded DEB file loading  GDEBI I get the message
ERROR: The dependancy cannot be satisfied : fpc-laz (=3.0.4). I cannot continue the installation any further.

Any hints anyone  ??

Title: Re: Lazarus Release 2.0.0
Post by: mdalacu on February 16, 2019, 04:13:54 pm
you should download and install the fpc and fpc-src packages first from here:
https://sourceforge.net/projects/lazarus/files/Lazarus%20Linux%20amd64%20DEB/Lazarus%202.0.0/
Title: Re: Lazarus Release 2.0.0
Post by: dbannon on February 18, 2019, 01:52:28 am
.....  GDEBI I get the message
ERROR: The dependancy cannot be satisfied : fpc-laz (=3.0.4). I cannot continue the installation any further.

Any hints anyone  ??
see -
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes#Debian_package_fpc_was_renamed_to_fpc-laz

That means that if you want to install the precompiled Lazarus binary from SourceForge, you must also use the fpc from the same place (as mdalacu said). You can no longer mix and match a fpc from your package manager AND use the SourceForge Lazarus. If you build your own Lazarus (and there is good reasons to do so http://wiki.freepascal.org/Installing_Lazarus_on_Linux#Build_Lazarus_from_Source ) you can first use either means of installing fpc.

Davo
Title: Re: Lazarus Release 2.0.0
Post by: nachoap on February 19, 2019, 06:00:58 pm
Hi again!

I've returned to Lazarus 1.8.4. One of my sqlite apps was losing a few characters in TEXT fields and sometimes showed then as chinesse characters :O :O :O.

I don't know if it's a Zeos or Lazarus problem. I've not time to uninstall last zeos lib and install previous. So I've downgraded to Lazarus 1.8.4. I'm working with both versions in my PC (Windows 10).

In a few days I'll try to see where is the problem.

Regards.
Title: Re: Lazarus Release 2.0.0
Post by: R.Blennerhed on February 20, 2019, 09:55:18 pm
Thanks for a good job of yours :D

Best regards/
Robert W. Blennerhed
Title: Re: Lazarus Release 2.0.0
Post by: tecnoxarxa on February 23, 2019, 02:36:46 am
Great job.Many thanks!
I love Object Pascal and Lazarus.

Kind Regards,
   German A.
Title: Re: Lazarus Release 2.0.0
Post by: SnoopyDog on February 24, 2019, 01:50:43 am
Thank you for this new release :)

I don't know if this bug was introduced in this version or earlier, but assigning "int64" and "qword" variables to and from "OleVariant" is implemented wrong in "variant.inc" (lazarus\fpc\3.0.4\source\rtl\inc).
Assigning an int64 or qword to OleVariant looses the higher 4 bytes because it calls "VariantManager. VarFromInt" for both cases. And in the other direction, "VarToInt64" and "VarToWord64" are exchanged.

This is the corrected code:

Code: [Select]
operator :=(const source : olevariant) dest : qword;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    dest:=variantmanager.vartoword64(variant(tvardata(source)));
  end;

operator :=(const source : olevariant) dest : int64;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    dest:=variantmanager.vartoint64(variant(tvardata(source)));
  end;

Code: [Select]
operator :=(const source : qword) dest : olevariant;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    variantmanager.olevarfromword64(dest,source);
  end;

operator :=(const source : int64) dest : olevariant;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    variantmanager.olevarfromint64(dest,source);
  end;

How can I get fpc compiled?
Title: Re: Lazarus Release 2.0.0
Post by: Cyrax on February 24, 2019, 02:11:36 am
Thank you for this new release :)

I don't know if this bug was introduced in this version or earlier, but assigning "int64" and "qword" variables to and from "OleVariant" is implemented wrong in "variant.inc" (lazarus\fpc\3.0.4\source\rtl\inc).
Assigning an int64 or qword to OleVariant looses the higher 4 bytes because it calls "VariantManager. VarFromInt" for both cases. And in the other direction, "VarToInt64" and "VarToWord64" are exchanged.

This is the corrected code:

Code: [Select]
operator :=(const source : olevariant) dest : qword;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    dest:=variantmanager.vartoword64(variant(tvardata(source)));
  end;

operator :=(const source : olevariant) dest : int64;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    dest:=variantmanager.vartoint64(variant(tvardata(source)));
  end;

Code: [Select]
operator :=(const source : qword) dest : olevariant;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    variantmanager.olevarfromword64(dest,source);
  end;

operator :=(const source : int64) dest : olevariant;{$ifdef SYSTEMINLINE}inline;{$endif}
  begin
    variantmanager.olevarfromint64(dest,source);
  end;

How can I get fpc compiled?

Hey, nice catch! I can see that it is same in the trunk version of FPC. Can you file a bug report so this won't be forgotten?

To compile your version of FPC, make sure that PATH environment variable contains path to FPC binary directory and then open terminal window/command prompt at the location of the FPC source directory. At the open terminal window/comman prompt execute this command : make all INSTALL_PREFIX=<path to your FPC binary directory>

Make sure that you make a backup of FPC binary directory before you rebuild FPC.