It looks as if for some reason the .lpr of your project omits the Interfaces unit.Lazarus 1.6.0 gives the same warning in that situation. I don't know how the update can affect it.
The Lazarus team is glad to announce the release of Lazarus 1.6.2. This is a bugfix release.
This release was built with FPC 3.0.0.
The previous release Lazarus 1.6.0 was built with FPC 3.0.0 too.
Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_1.6.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.0
Also if 1.6.0 and 1.6.2 are both built with FPC3.0.0, how is it this is shown to have changes ?There aren't any. Perhaps you could better read it as "Available features and changes that have been introduced with FPC 3.0.0".
but if this is 1.6.2, why are the release notes for 1.6.0 ?1.6.2 is a bug fix release. So there are no new features. Hence no release notes.
Also if 1.6.0 and 1.6.2 are both built with FPC3.0.0, how is it this is shown to have changes ?The changes are both for the last major release.
It looks as if for some reason the .lpr of your project omits the Interfaces unit.Lazarus 1.6.0 gives the same warning in that situation. I don't know how the update can affect it.
Maybe there are mixed .ppu and .o files from the old revision. Just rebuild Lazarus and its packages clean. Usually it solves all problems.
sudo apt-get install gdb
whereis gdb
You should get something like this:gdb: /usr/bin/gdb
and add it manually (or browse to it).
@tr_escape
Install debugger on Debian/mint/ubuntu:Code: [Select]sudo apt-get install gdb
If gdb is installed, but you get the same message for some reason, try adding it manually:
first, find out where is gdb installed:Code: [Select]whereis gdb
You should get something like this:Code: [Select]gdb: /usr/bin/gdb
and add it manually (or browse to it).
I would like it very much if Lazarus and the controls finally started to recognize it when you have your Windows taskbar in another location then at the bottom.
IIRC. the previous version at least recognized it when you maximized the main Lazarus window, but now it pops behind the taskbar.
It also tends to restore the windows at the wrong location.
gdk_monitor_get_workarea ()
void
gdk_monitor_get_workarea (GdkMonitor *monitor,
GdkRectangle *workarea);
Retrieves the size and position of the “work area” on a monitor within the display coordinate space. The returned geometry is in ”application pixels”, not in ”device pixels” (see gdk_monitor_get_scale_factor()).
The work area should be considered when positioning menus and similar popups, to avoid placing them below panels, docks or other desktop components.
Note that not all backends may have a concept of workarea. This function will return the monitor geometry if a workarea is not available, or does not apply.
Parameters
monitor
a GdkMonitor
workarea
a GdkRectangle to be filled with the monitor workarea.
SystemParametersInfo function with the SPI_GETWORKAREA value.
@dogriz,
Thank you so much gdb issue is solved.
But I had to remove lazarus 1.6.2 and I reinstalled the 1.6.0 for now.
I'll try later.
I think there is a issue inside of UTF8SearchInStringList function.Indeed it calls UTF8CompareText which was changed in trunk / r51977 by Bart and then merged to 1.6.1 fixes branch.
line 1648
// project uses lcl unit Forms if (UTF8SearchInStringList(MainUsesSection,'interfaces')>=0) or (UTF8SearchInStringList(ImplementationUsesSection,'interfaces')>=0) then
and I changed to this lines:
line 1648
// project uses lcl unit Forms if (UTF8SearchInStringList(MainUsesSection,'Interfaces')>=0) or (UTF8SearchInStringList(ImplementationUsesSection,'Interfaces')>=0) then
function UTF8SearchInStringList(List: TStrings; const s: string): integer;
begin
if List=nil then exit(-1);
Result:=List.Count-1;
while (Result>=0) and (UTF8CompareText(List[Result],s)<>0) do dec(Result);
end;
Can you undo the changes above an try this?
If you go to the ($Lazarus)/ide/ideprocs unit, line 1286Code: [Select]function UTF8SearchInStringList(List: TStrings; const s: string): integer;
begin
if List=nil then exit(-1);
Result:=List.Count-1;
while (Result>=0) and (UTF8CompareText(List[Result],s)<>0) do dec(Result);
end;
and change UTF8CompareText to CompareText, does it also fix your problem?
(All unitnames are in ASCII, so there currently is no need to use Utf8 functions in that code).
If this also solves your problem, this indicates that there is an issue with Utf8CompareText or WideCompareText.
Also, if this fixes it, what is your locale?
Bart
Please file a bugreport:
Describe the steps you have done to IDEProcs unit.
Mention your local.
Add a reference to this thread (preferrably pointing to your message where you described this).
In your locale: what is the result of WideUpperCase('interfaces') and what is the result of WideLowerCase('INTERFACES') ?
The same for WideUpperCase(Utf8ToUtf16('interfaces')) and WideLowerCase(Utf8ToUtf16('INTERFACES'))
And to make sure: what is teh result of WideCompareText('interfaces','INTERFACES')?
From wikipedia (https://en.wikipedia.org/wiki/Turkish_alphabet):
The letters Q, W, and X of the ISO basic Latin alphabet do not occur in the Turkish alphabet (replacements for these letters are K, V and KS), while dotted and dotless I are distinct letters in Turkish so that "i" does not become "I" when capitalized.
This may very well be the root cause of your problem.
Bart
I created a bug report http://bugs.freepascal.org/view.php?id=30967 (http://bugs.freepascal.org/view.php?id=30967)
Unfortunately, with Lazarus 1.6.2 on Mac OS X 10.10.5, when I try to open a package file, Lazarus locks up. I get the spinning beach ball of death and have to kill Lazarus. :(
A lock up is happening in a TSaveDialog in a compiled application. I will go back to 1.6.0 for now. :(Can you please test which revision causes the regression against 1.6.0. It may be related to this:
line 1648
// project uses lcl unit Forms if (UTF8SearchInStringList(MainUsesSection,'interfaces')>=0) or (UTF8SearchInStringList(ImplementationUsesSection,'interfaces')>=0) then
A lock up is happening in a TSaveDialog in a compiled application. I will go back to 1.6.0 for now. :(Can you please test which revision causes the regression against 1.6.0. It may be related to this:
http://bugs.freepascal.org/view.php?id=29694
and its related / duplicate issues.
Info about all merged revisions:
http://wiki.freepascal.org/Lazarus_1.6_fixes_branch#Fixes_for_1.6.2_.28merged.29
I have been using the patch for Issue #29694 for a long time, so it is not that alone. I'll see if I can figure anything out though.The 1.6.2 version had some ~200 commits. You could try bisecting over them:
I wonder why FPC-3.1.1 is not shipped with ??Because it is a development version. Lazarus is released only with a release version of FPC.
What is the difference between lazarus_1.6.2-0_amd64.deb and lazarus-project_1.6.2-0_amd64.deb?I think Mattias only renamed it to prevent a name clash with packages provided by Linux distributions.
The Lazarus team is glad to announce the release of Lazarus 1.6.2. This is a bugfix release.
This release was built with FPC 3.0.0.
The previous release Lazarus 1.6.0 was built with FPC 3.0.0 too.
Here is the list of changes for Lazarus and Free Pascal:
http://wiki.lazarus.freepascal.org/Lazarus_1.6.0_release_notes
http://wiki.lazarus.freepascal.org/User_Changes_3.0.0
The release is available for download on SourceForge:
Hello,
I switched from verze1.4.4 to version 1.6.2 and features UTF8ToAnsi not convert Czech accented characters, the character still has a length of two characters. Discuss where to complain or to replace it.
Thank you
Peter
http://sourceforge.net/projects/lazarus/files/
Choose your CPU, OS, distro and then the "Lazarus 1.6.2" directory.
Checksums for the SourceForge files:
http://www.lazarus-ide.org/index.php?page=checksums#1_6_2
Minimum requirements:
Windows:
MS Windows >= Win98 (32 or 64bit)
Win98 and WinNT IDE needs FPC 2.6.4 and building with flag
-dWIN9XPLATFORM.
FreeBSD/Linux:
gtk 2.8 or qt4.5, 32 or 64bit.
Mac OS X:
10.5 to 10.11, LCL only 32bit, non LCL apps can be 64bit.
The svn tag is
http://svn.freepascal.org/svn/lazarus/tags/lazarus_1_6_2
Here is the list of fixes for Lazarus 1.6.x:
http://wiki.freepascal.org/Lazarus_1.6_fixes_branch
For people who are blocked by SF, the Lazarus releases from SourceForge
are mirrored at:
ftp://freepascal.dfmk.hu/pub/lazarus/releases/
and later at (after some time for synchronization)
http://michael-ep3.physik.uni-halle.de/Lazarus/releases/
and
http://mirrors.iwi.me/lazarus/
I think Mattias only renamed it to prevent a name clash with packages provided by Linux distributions.
I think Mattias only renamed it to prevent a name clash with packages provided by Linux distributions.
But, both are shown for download and the file sizes are slightly different, should I install both and if so, which order?
If not, which one to install then?
ftp://freepascal.dfmk.hu/pub/lazarus/releases/Lazarus%20Linux%20amd64%20DEB/Lazarus%201.6.2/
But, both are shown for download and the file sizes are slightly different, should I install both and if so, which order?Just install one. They should be identical, I don't know what causes the size difference.
If not, which one to install then?
I dont know what Linux you are using, but I have found it easiest to let Synaptic install Lazarus. In Debian Stretch it's just a matter of selecting Lazarus 1.6.2 and click install. The right version of FPC and sources are installed automatically at the same time.Unfortunately many distributions have very old versions of FPC and Lazarus. Then the new packages provided here are important.
Bros, I discovered stable versions of FPC/Lazarus (3/1.6) in Debian legacy repo. That's great! But how long to wait for stables in mainline repo?
That's a question best asked to Debian core. We don't control that.
Lazarus 1.6.2 and FPC 3.0.0 are in Debian testing. Just FYI.
Which means that they will find their way into the next stable.
I guess enabling the 'testing' Debian repository, or the backports, will give you 1.6.2/3.0.0.
I use Debian, but I never use the Debian implementation of Lazarus/FPC because they split up the installation into multiple small packages, for no apparent reason other than to make it more complicated than it needs to be. I use the .deb packages from the Lazarus downloads area (just three packages), and these work fine.Yeah, it is best solution for sure but deb-package now avail for x64 only (btw it was fixed to 1.6.2.1 after bug-report of mine :)) ! I badly need it for arm!