On Mon, 26 Jul 2010 14:49:02 +0200
Jonas Maebe wrote:
>
> On 26 Jul 2010, at 14:18, Bernd Kreuss wrote:
>
> > What is the easiest way to have a second installation of FPC around that
> > I can easily switch to on the same machine without having to change half
> > a dozen paths and moving config
Jonas Maebe wrote:
... How to combine this with Lazarus, I don't know.
Lazarus has the --pcp= commandline option which defines the primary
configuration path, hence the location of the FPC compiler binary and
library sources. I've copied the source tree into an appropriate place
in /usr/loc
I use symbolic links. I created /opt/fpc directory which contains subdirectories for each version I have available. /opt/fpc/fpc-current is a symbolic link to the directory of the version of fpc I am currently using. /opt/fpc/bin is a symbolic link to /opt/fpc/fpc-current/bin. In order to switc
On 26 Jul 2010, at 14:18, Bernd Kreuss wrote:
> What is the easiest way to have a second installation of FPC around that
> I can easily switch to on the same machine without having to change half
> a dozen paths and moving config files around?
Personally, I never actually install my development
Currently I have the latest svn of FPC installed (make install) which
results in all files being installed where they belong, the binary being
in the search path and fpc.cfg in /etc and I can easily use it with Lazarus.
Now I want to test something I wrote whether it will compile with an
older ver
