Sign in Join

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

Mailing lists / fpc-devel / 2006-05

setup for testing changes between 2.0.2, 2.0.x and 2.1.1

8 messages · 5 people · –

Reply by email Subscribe to this list Your subscription

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

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

Regards,
- Graeme -

There's no place like 127.0.0.1

Reply by email

Daniël Mantione
to Graeme Geldenhuys

Op Thu, 18 May 2006, schreef Graeme Geldenhuys:

Show quoted text 12 lines
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).

Daniél

Reply by email

Joost van der Sluis
to Daniël Mantione
Daniël Mantione wrote 18 lines
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

Reply by email

Graeme Geldenhuys
to Joost van der Sluis
Joost van der Sluis wrote
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

This sounds like a easy way or doing it, thanks!
Can one change the installation path with the "make install" command? I could never figure this out, so always did a "make zipinstall" and then unpack it to my desired location. I prefer the /opt path as that is where my Lazarus install lives.

Regards,
Graeme.

There's no place like 127.0.0.1

Reply by email

Marco van de Voort
to Joost van der Sluis: ? If you upgrade from svn, just do 'make install', then 2.0.x will be placed in…
Show quoted text 12 lines
> > 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.
If you name them ppc386-2.1.1 and ppc386-2.0.2, then iirc you can choose
which one you want per compile;

fpc -V2.1.1 compileme.pp

or

fpc -V2.0.2 compileme.pp

Reply by email

Graeme Geldenhuys
to Graeme Geldenhuys: This sounds like a easy way or doing it, thanks! Can one change the installation path…

Thanks to everybody that helped. I managed to setup 3 versions of FPC in my home directory and changed the fpc.cfg file to use the $fpcversion instead of a hardcoded version. All works perfectly.

All these tips should be place in a FAQ or WIKI somewhere if it hasn't already!

Regards,
- Graeme -

Graeme Geldenhuys wrote 19 lines
On 5/18/06, Joost van der Sluis wrote: > 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 This sounds like a easy way or doing it, thanks! Can one change the installation path with the "make install" command? I could never figure this out, so always did a "make zipinstall" and then unpack it to my desired location. I prefer the /opt path as that is where my Lazarus install lives. Regards, Graeme. -- There's no place like 127.0.0.1
There's no place like 127.0.0.1

Reply by email