[fpc-devel] setup for testing changes between 2.0.2, 2.0.x and 2.1.1

[Joost van der Sluis]

On Thu, 2006-05-18 at 17:07 +0200, Daniël Mantione wrote:
> Op Thu, 18 May 2006, schreef Graeme Geldenhuys:
> > Hi,
> > What is a recommend setup so I can easily switch between the 2.0.2 and
> > 2.0.x and 2.1.1 versions for testing fixes/changes and what impact
> > they would have on my applications.
> > 
> > I just got a confirmation from Mantis that one of the bugs I reported
> > has been fixed in 2.0.x and a fix and possible speed increase change
> > have been made in 2.1.1 and if I could test 2.1.1.   How do I go about
> > such a setup.  I don't want to remove 2.0.2 and I use it for our
> > commercial development work.
> > 
> > I am currently running on GNU/Linux and have 2.0.2 installed in /opt/fpc
> 
> Simply install them in different directories. I often just use -n and use 
> -Fu on the command line to point the compiler to the right rtl. If this is 
> to uncomfortable, you can make the configuration file conditional, it 
> supports #ifdef constructions (check documentation).

?

If you upgrade from svn, just do 'make install', then 2.0.x will be
placed in /usr/local/lib/fpc/2.0.x and 2.1.x in /usr/local/lib/fpc/2.1.1

Change your fpc.cfg to use $fpcversion instead of 2.x.x

And make two symlinks in /usr/bin, one which is called ppc386_2_1_x and
one which is called ppc386_2_0_x.

This makes upgrading very easy for both (make install) and you can
choose your compiler-version with choosing the right name. (I also have
a 'default' ppc386 link, which in my case is 2.1.1

Regards,
  Joost