In our previous episode, Tomas Hajny said:
> Are they?
>
> Anyway - as far as I can see, the usual solution appearing with other
> programs on MS Windows is either defaulting new version to the directory
> used for the previous one and/or suggestion that you should uninstall the
> previous version
On Fri, March 14, 2014 16:33, Bart wrote:
>> As for whether it should ask... well, perhaps, but that does complicate
>> things...
>
> Complications are good.
Are they?
Anyway - as far as I can see, the usual solution appearing with other
programs on MS Windows is either defaulting new version to
On 14/03/2014 16:33, Bart wrote:
> On 3/14/14, Reinier Olislagers wrote:
>
>> I wouldn't expect the installer to automatically put your new fpc before
>> anything else as it can mess up batch scripts that expect certain
>> binaries etc (say Delphi make or some special grep).
>
> Every which way
On 3/14/14, Reinier Olislagers wrote:
> I wouldn't expect the installer to automatically put your new fpc before
> anything else as it can mess up batch scripts that expect certain
> binaries etc (say Delphi make or some special grep).
Every which way you loose?
> As for whether it should ask.
On 14/03/2014 14:23, Bart wrote:
> I installed 2.6.4 for win32.
> I removed the 2.6.4rc1 installation.
> After that I wanted to rebuild Lazarus, so I did a "make clean all" in
> Lazarus dir, but got only errors.
> This was because make was now the make from D7, because the installer
> appended the
Hi,
I installed 2.6.4 for win32.
I removed the 2.6.4rc1 installation.
After that I wanted to rebuild Lazarus, so I did a "make clean all" in
Lazarus dir, but got only errors.
This was because make was now the make from D7, because the installer
appended the path to fpc (so it was last).
Easily fix
