Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2010-09

Multiple profile directories

4 messages · 2 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mark Morgan Lloyd

When running with multiple profile directories (--pcp option), is it possible to put something in (a file in) the default ~/.lazarus so that if it's used there's a warning on startup e.g. "You're running with the default profile, do you really want to do this?".

I'm not talking about an automatic facility here, just something that a developer can insert or enable manually as a reminder to himself.

At the same time, could a quick check be run that the FPC version is as expected?

I was bitten by both of these over the weekend when trying to compare the behaviour of different versions of lazarus, one of which wanted a different FPC version.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email

Mattias Gaertner
to Mark Morgan Lloyd
Show quoted text 7 lines
When running with multiple profile directories (--pcp option), is it possible to put something in (a file in) the default ~/.lazarus so that if it's used there's a warning on startup e.g. "You're running with the default profile, do you really want to do this?". I'm not talking about an automatic facility here, just something that a developer can insert or enable manually as a reminder to himself.

Is an error messages sufficient?

At the same time, could a quick check be run that the FPC version is as expected?

As expected?
One IDE can work with multiple FPC versions.

I was bitten by both of these over the weekend when trying to compare the behaviour of different versions of lazarus, one of which wanted a different FPC version.

Mattias

Reply by email

Mark Morgan Lloyd
to Mattias Gaertner
Mattias Gaertner wrote 12 lines
On Mon, 13 Sep 2010 09:02:46 +0000 Mark Morgan Lloyd wrote: > When running with multiple profile directories (--pcp option), is it > possible to put something in (a file in) the default ~/.lazarus so that > if it's used there's a warning on startup e.g. "You're running with the > default profile, do you really want to do this?". > > I'm not talking about an automatic facility here, just something that a > developer can insert or enable manually as a reminder to himself. Is an error messages sufficient?

I think so. Something that can be removed so the directory can be used as a template for a new copy.

Show quoted text 5 lines
> At the same time, could a quick check be run that the FPC version is as > expected? As expected? One IDE can work with multiple FPC versions.

I wasn't able to rebuild 0.9.26.2 while ppc386 -> 2.4.0 (working from memory), I had to revert to 2.2.4. So possibly a warning if the compiler version has been changed since the last successful run.

Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues]

Reply by email

Mattias Gaertner
to Mark Morgan Lloyd
Show quoted text 26 lines
Mattias Gaertner wrote: > On Mon, 13 Sep 2010 09:02:46 +0000 > Mark Morgan Lloyd wrote: > >> When running with multiple profile directories (--pcp option), is it >> possible to put something in (a file in) the default ~/.lazarus so that >> if it's used there's a warning on startup e.g. "You're running with the >> default profile, do you really want to do this?". >> >> I'm not talking about an automatic facility here, just something that a >> developer can insert or enable manually as a reminder to himself. > > Is an error messages sufficient? I think so. Something that can be removed so the directory can be used as a template for a new copy. >> At the same time, could a quick check be run that the FPC version is as >> expected? > > As expected? > One IDE can work with multiple FPC versions. I wasn't able to rebuild 0.9.26.2 while ppc386 -> 2.4.0 (working from memory), I had to revert to 2.2.4. So possibly a warning if the compiler version has been changed since the last successful run.

There is an error when building with an older fpc version. Of course we can't add an error for future fpc versions. Maybe a warning could be added for untested fpc versions and what version is recommended.

Mattias

Reply by email