Compiling lazarus

[JuhaManninen]

FPC is in $PATH after installing Lazarus 2.2, right? In your GitLab main directory run "make clean all" or "make clean bigide". Then start Lazarus.exe from the cmd line.
Build it again from Lazarus Tools menu with all the debug flags. There is a "Debug IDE" profile to choose.
You can choose more packages to install before building.
Don't copy any directories from the 2.2 release.

[duzenko]

FPC is in $PATH after installing Lazarus 2.2, right?

No, do I need to add it to PATH?
I've been running it with full path to make.exe, i.e.

Code: Pascal  [Select][+][-]

1. C:\dev\lazarus22\fpc\3.2.2\bin\i386-win32\make

[duzenko]

Anyway, I was able to resolve it with checking the clean checkbox in Lazarus GUI
And breakpoints worked after I switched to debug profile

[JuhaManninen]

No, do I need to add it to PATH?
I've been running it with full path to make.exe, i.e.

Code: Pascal  [Select][+][-]

1. C:\dev\lazarus22\fpc\3.2.2\bin\i386-win32\make

The Makefiles call fpc. It must be in PATH. Then also "make" and some scripts are found without specifying the full path.
The Lazarus installer sets the PATH if I remember right. At least it should.
I use Windows only seldom myself. I am not sure.

[Alex_Krivtsov]

Following Reply#7 (thanks to Martin_fr) I compiled Lazarus to new LazDebug folder under x64 windows 10. 'Run' for Lazarus project brings the empty form template.
I tryed to open my HelloWorld project (Project-Open Project) and got a crush of Lazarus been debugged with opened empty OpenDialog window.
Trying to find the cause I set a breakpoint at the start of OpenProject(aMenuItem: TIDEMenuItem) procedure in SourceFileManager unit. Neither this nor others relyable breakpoints worked.
To get sure of compiled lazarus.exe I launched it without debugger - it asked me to update configuration, then worked properly.
I put Lazdebug\lazarus.exe to the 'Host application' of Run parameters in lazarus project and pressed F9 - my HelloWorld opened (I'd loaded it when testing compiled Lazarus without debugger). I run it - debugger functions (breakpoints, watches, callstack) worked properly. But any OpenDialog.execute crached the Lazarus in the same way.
Having breakpoints operable I reached the call of external (stdcall convention) method ADialog.Show(GetParentWnd) of IModalWindow interface, which hangs forever. Screenshot of the point may be useful.
 

[Martin_fr]

But any OpenDialog.execute crached the Lazarus in the same way.

Have you tested with the new Lazarus 3.0 RC1 (or fixes branch)?

It is known, that (on some Windows installations) any app (including the IDE itself) that uses open/save/dir/... dialogs will hang.

However according to the reports, Lazarus 3.0 does not have the issue.



The call you show in your screen shot does not help to identify the issue.

The call to the interface will eventually end up in the W32 API. And Windows will handle the call.
Since the issue happens on some, but not all installations of Windows, it is likely that some shell-handler called by the OS, is triggering something that causes the issue. Though it could be anywhere else...