Lazarus Release 2.0.0

[mattias]

The Lazarus team is glad to announce the release of Lazarus 2.0.0.

• This release was built with FPC 3.0.4.
• The previous release Lazarus 1.8.4 was built with FPC 3.0.4 as well.

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/

[nouzi]

  thank lazaurs and freepascal  team 

[Igor Kokarev]

Thanks for your great work!

[gerardus]

Thank you for your excellent work!

[Elfrom]

Thanks for doing this great effort.
Lots of love goes out to Lazarus and FPC-team

[guest62577]

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;

[howardpc]

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...

[balazsszekely]

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.

[mmvisual]

WARNIG !!!! This Lazarus Release 2.0.0 is buggy !!!!

The code is running before the creation from all elements are finished !!! 

See pictures.

[howardpc]

I fail to see why you are attributing a SIGSEGV to LCL code rather than code you have written.

[mmvisual]

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.

[mmvisual]

The define from the variable is here:

[mmvisual]

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 

PS: I have write this bug in the thread from RC3 - but it was ignored.

[Martin_fr]

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:

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.

[guest58172]

Thanks to all the contributors for this nice release.