(Dreams)
In addition, I would like the release to include an RTL version compiled with and without debug information. It would be nice to be able to switch between them.
That way, debugging non-user code would also be a pleasant and convenient experience.
That is actually something that I have started to look into.
And it may work with Lazarus 4.99 due to the build system changes Mattias recently made (I haven't fully tested if they indeed fix the issues I had).
The perfect solution here would be the still upcoming FPC sub-targets. (e.g. planed for wide vs ansi char RTL). Then it would be easy to switch.
But in theory a 2nd FPC build can (ON WINDOWS !!!) be installed into a different folder. Then in the IDE that can be changed (in project settings).
However, the IDE did not pick up correctly => it was required to manually do a clean build, and ensure packages are rebuild. Otherwise it would just error out.
Mind: as far as my involvement here goes, this is Windows only.
And also, I have to decide how many build I add. Running he build is cheap. Just run the script and wait. But each build needs to have some testing before it goes out, that takes time.
Also, that would not come with any comfort at this stage. I.e. there wouldn't be any setup to have the packages ppu in different folders. So they have to all rebuild on every change...
In addition to the build-system (full rebuild need), using it with current (4.8 ) release has another flaw. If build with run time checks -Criot, then the debugger steps into (F7) methods like fpc_check_object, if you try to step into a virtual method. Lazarus 4.99 has "excluded routines" where that can be listed, so the debugger will not step into it.
Recent
