<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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 switch versions I just need to modify the /opt/fpc/fpc-current link.<div><br></div><div>My fpc.cfg file has unit/library/include references similar to this: -Fu/opt/k-/fpc/fpc-current/lib/fpc/$fpcversion/units/$fpctarget</div><div>So it works with any version I install.</div><div><br></div><div>Here are the ugly notes I made when I set it up on my development box:</div><div><br></div><div><div> - First time retrieve from Subversion</div><div> cd /opt/fpc</div><div> - Stable branch</div><div> svn checkout <a href="http://svn.freepascal.org/svn/fpc/branches/fixes_2_2">http://svn.freepascal.org/svn/fpc/branches/fixes_2_2</a> fpc</div><div> - Development branch (v2.1.1)</div><div> svn checkout <a href="http://svn.freepascal.org/svn/fpc/trunk">http://svn.freepascal.org/svn/fpc/trunk</a> fpc</div><div> mv fpc fpc-<version>-svn</div><div> rm fpc-source</div><div> ln -s fpc-<version>-svn fpc-source</div><div><br></div><div> - Update the source from Subversion</div><div> cd /opt/fpc/fpc-<version>-svn</div><div> svn update</div><div><br></div><div> - Complile</div><div> cd /opt/fpc/fpc-<version>-svn</div><div> make OPT='-gl' zipinstall</div><div><br></div><div><div> Install the new zip</div><div> cd /opt/fpc</div><div> rm fpc-current</div><div> mkdir v<version>.<date></div><div> ln -s v<version>.<date> fpc-current</div><div> cd fpc-current</div><div> tar -zxvf ../fpc-source/fpc-<version>.<cpu>-<arch>.tar.gz</div><div> cd bin</div><div> ln -s ../lib/fpc/<version>/ppc386 .</div></div><div>
<div style="font-family: Helvetica; "><br class="Apple-interchange-newline"><br></div><span class="Apple-style-span" style="font-family: Helvetica; ">Lloyd B. Park</span><span class="Apple-style-span" style="font-family: Helvetica; "><br></span><span class="Apple-style-span" style="font-family: Helvetica; "><a href="mailto:lloyd.b.park@gmail.com">lloyd.b.park@gmail.com</a></span><span class="Apple-style-span" style="font-family: Helvetica; "><br></span><span></span><span><img height="167" width="111" id="54d4eca7-a488-46ce-b6ca-5144e8d4532c" apple-width="yes" apple-height="yes" src="cid:3334197965_213123"></span>
</div>
<br><div><div>On Jul 26, 2010, at 8:18 AM, Bernd Kreuss wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Currently I have the latest svn of FPC installed (make install) which<br>results in all files being installed where they belong, the binary being<br>in the search path and fpc.cfg in /etc and I can easily use it with Lazarus.<br><br>Now I want to test something I wrote whether it will compile with an<br>older version of FPC and I even need to recompile the entire Lazarus<br>with the older FPC because it is a patch for Lazarus itself.<br><br>What is the easiest way to have a second installation of FPC around that<br>I can easily switch to on the same machine without having to change half<br>a dozen paths and moving config files around?<br><br>I have thought about switching compilers system-wide by simply having<br>two compiled versions in two separate directories lying around and then<br>simply "make install" in one of them or in the other one to switch<br>between them. Does this make sense or is there a better (recommended)<br>way of doing this?<br>_______________________________________________<br>fpc-pascal maillist - <a href="mailto:fpc-pascal@lists.freepascal.org">fpc-pascal@lists.freepascal.org</a><br><a href="http://lists.freepascal.org/mailman/listinfo/fpc-pascal">http://lists.freepascal.org/mailman/listinfo/fpc-pascal</a><br></div></blockquote></div><br></div></body></html>