Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?Not sure where/when this recommendation came to be....
I searched a bit, and the main issue (before Laz1.8 ) was SEH-handling, but that was before Laz1.8.SEH is now used by both 32 and 64 FPC for bit Windows.
A second main issue was, that cross-compiling from Laz/FPC-64Bit to 32-Bit was buggy
Is it just me, or there is no way to install over the previous installation so that the configuration (installed components etc.) would be taken over?
I know it needs the IDE to get re-compiled, and that is not a problem to do, but I didn't found any other way to do it except to install every single component again.
I am still at 2.2.0 RC2 because of this
- I just do not want to take the risk for my setup to get lost.
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?IIRC The problem with cross compiling win64 to win32 is that the win64 platform does not know Extended (80bit float) type. Solution is software support for this type, but I don't know how much progress is being made on it, and probably only in trunk.
Quick question: Is it still the "official" recommendation, to use the 32-Bit Version of Lazarus on 64-Bit Windows, and then rather to cross-compile your project to 64-Bit?IIRC The problem with cross compiling win64 to win32 is that the win64 platform does not know Extended (80bit float) type. Solution is software support for this type, but I don't know how much progress is being made on it, and probably only in trunk.
can I ask which FPC branch/tag at gitlab this Lazarus release uses ?
can I ask which FPC branch/tag at gitlab this Lazarus release uses ?
For Windows:
Tag release_3_2_2
SHA-1: 0d122c49534b480be9284c21bd60b53d99904346, Branch RevNo: 53220
* * requiredversion to 3.2.0 and 3.2.2
Eh support for specific calling conventionsThose sound like FPC features?
hasn't made it to release yet.
Eh support for specific calling conventionsThose sound like FPC features?
hasn't made it to release yet.
Then they will make it, when fpc does a release containing them.
I don't know if that will be 3.2.4 or 3.4.
Nor do I know when either of them will be released.
(You can but that query in the fpc section of the forum, or better (probably better likelihood to be seen by more fpc devs) on the fpc mail list.)
If/When either of them is released, Lazarus is likely to make a release soon after.
Cross debugging used to be an issue.
But it is no longer if you use the 64 bit IDE.
- The 64bit FpDebug can handle 64 and 32 bit projects.
- GDB can do both do, but needs a helper app (which is part of the setup)
These directives have been in the stable fpc branch for a long time (I can’t say from which version), but they are not supported by the lazarus text editor. Parsing errors will cause irritation. I wrote a patch for this case, but it's still in the main branch.Ok, I see.
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.I haven't tested that, so I don't know.
With 2.2.0 I was a little afraid that Lazarus development could be ceased, but I'm happy to see that development is continuing! 👍Just monitor https://gitlab.com/freepascal.org/lazarus/lazarus/-/commits/main and you will see the progress.
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.
Does this also mean, that cross-compiling from Lazarus/FPC x64 to Linux x64 is possible now? I used to get "internal error 200208151" in this case.
Probably not. You can't crosscompile from a target that doesn't have 80-bit extended to one that does. Or at least that is currently not supported.
Note that codetyphon packages FPC versions that are not stable releases.
Yes, that's the exactly the point which I do not understand: From Win64 to Linux64 -> same architecture, so both do not have Extended. But it doesn't work anyway ::)
the extended type is available on all Intel x86 processors, except on the Windows 64-bit platform
So if I go back to using 32bit-Lazarus, I should be able to cross-compile both for Win64 and Linux64, right?
Hi,
I'm using lazarus in portable mode on a USB key.
Before installation, I create in the directory dedicated to lazarus a file named "lazarus.cfg" containing these values "--primary-config-path=e:\lazarus_2.2.2\lazconfig".
When I add the installation package "sqlite3laz", and the application recompiles, I get an error message when I launch it (see the attachment). Is this normal?
With version 2.2.0, I didn't have it.
Thank you
Win 10, Display text size = 200% (Laptop high resolution)Luckily I noticed this and added the line in 59eeb39742. Will be merged to fixes branch.
Project -> Options -> Custom Options -> All Options
displays like in the attachment.
in ide\allcompileroptions.pas at lines near 350, adding
Container.Perform(CM_PARENTFONTCHANGED, 0, 0) corrects the line spacing.
Container := sbAllOptions; Container.Perform(CM_PARENTFONTCHANGED, 0, 0); // ~bk Container.DisableAutoSizing{$IFDEF DebugDisableAutoSizing}('TfrmAllCompilerOptions.RenderAndFilterOptions'){$ENDIF};
Cannot Debug Win32/Release Application in Lazarus IDE
I confirm what RadDeveloper said is reproducible on Lazarus 2.2.2 Linux GTK2.Also in old 2.2.0.
Thank you for the reply.Cannot Debug Win32/Release Application in Lazarus IDE
Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?
Thank you for the reply.Cannot Debug Win32/Release Application in Lazarus IDE
Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?
GNU debugger(dbg.exe) falls in the error above I mentioned.
Execution stopped with exit-codeThis usually means that your app was started [(1)] (and for that you must have some debugger (if your setting is gdb, then some gdb.exe)), and your app did then quit
Yes I do have 64-bit installed on Windows, plus FPC addon. Seems like correct path with placeholders included were not edited since out of box installation, so I had to put them manually.Thank you for the reply.Cannot Debug Win32/Release Application in Lazarus IDE
Is your Lazarus installation 64 bit or 32 bit?
What debugger you use, FpDebug or GDB (Project/Project options/Project options/Debugger)?
GNU debugger(dbg.exe) falls in the error above I mentioned.
You probably don't have 32-bit gdb installed (under Lazarus install directory\mingw, 32-bit in i386-win32\bin\gdb.exe and 64-bit in x86_64-win64\bin\gdb.exe).
Or your app depends on some dll, that you did not put in the new install?No, it's blank TForm 32 bit app. AV is off.QuoteExecution stopped with exit-codeThis usually means that your app was started [(1)] (and for that you must have some debugger (if your setting is gdb, then some gdb.exe)), and your app did then quit
[(1)] The exe file was opened by the OS, but it may (or may not) have failed before any code was executed.
- This could be, that the IDE config is hard coded to the 64 bit debugger (though IIRC that causes a diff error).
- Or it could be, that the OS failed to load dependencies.
- Or it could be that your Anti-Virus killed the process.