Re: [Lazarus] Different paths, different computers, and one project
On Sat, Jul 7, 2018 at 11:52 PM, Marcos Douglas B. Santos wrote: > Imagine a project that works only with set of unit paths (-Fu), not packages. > The issue is that a computer could have a different path for a lib, > comparing to another one. > > I've removed the paths from the project (.lpi) and added an > `@extrafpc.cfg` with `-Fu` and `-Fl` paths. I can compile the project, > but the code-completion doesn't work because the IDE can't find the > units. > I can't also use `Other sources` option cause it will have the same > problem using `-Fu` and hard-coded paths. > > How to configure the paths? I've used the $Env(name) and it worked. The $Env is the best option in that case? -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Debugging Lazarus using Lazarus
On 07/07/18 10:45, Martin Frb via Lazarus wrote: On 07/07/2018 11:46, Mark Morgan Lloyd via Lazarus wrote:> When multiple copies of the same version (e.g. trunk) Lazarus are > being run, with a view to stepping through a problem in IDE-related > code, is there any way to force an override so that all windows > associated with the "inner" copy are marked distinctively with e.g. an > implausible background colour, a thin diagonal line overlaying the > content, or at the very least an instance identifier in every caption?>In menu Run > Run Parameter, specify --primary-config-path=/somefolder - Then on first run, go into options > editor > colors, and change whatever color you like. (e.g. background or gutter). well ok that is only the editor windows. It will not affect breakpoints, etc- The main IDE bar has/has not the word "debugging" in it.- You can also have a different projects open. As the last open project will be re-open, and that is stored in primary conf. With that, the debugged IDE will not open the stack and watches window (unless you want it to). I've got /two/ main editor bars with "debugging" in them, two windws called "Source Editor (2)" and so on :-) I'd have thought that a comparatively easy way round this would have been a global option to put the main-process PID on all form/dialogue captions. That would have result in a useful distinction even when multiple instances were using the same configuration files. But I'm not volunteering to do it this weekend ;-) -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
Re: [Lazarus] Debugging Lazarus using Lazarus
On 07/07/2018 11:46, Mark Morgan Lloyd via Lazarus wrote: When multiple copies of the same version (e.g. trunk) Lazarus are being run, with a view to stepping through a problem in IDE-related code, is there any way to force an override so that all windows associated with the "inner" copy are marked distinctively with e.g. an implausible background colour, a thin diagonal line overlaying the content, or at the very least an instance identifier in every caption? In menu Run > Run Parameter, specify --primary-config-path=/somefolder - Then on first run, go into options > editor > colors, and change whatever color you like. (e.g. background or gutter). well ok that is only the editor windows. It will not affect breakpoints, etc - The main IDE bar has/has not the word "debugging" in it. - You can also have a different projects open. As the last open project will be re-open, and that is stored in primary conf. With that, the debugged IDE will not open the stack and watches window (unless you want it to). -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
[Lazarus] Debugging Lazarus using Lazarus
When multiple copies of the same version (e.g. trunk) Lazarus are being run, with a view to stepping through a problem in IDE-related code, is there any way to force an override so that all windows associated with the "inner" copy are marked distinctively with e.g. an implausible background colour, a thin diagonal line overlaying the content, or at the very least an instance identifier in every caption? -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- ___ Lazarus mailing list Lazarus@lists.lazarus-ide.org https://lists.lazarus-ide.org/listinfo/lazarus
