In Windows, I was maintaining fpc 20x and fpc211 at various times. My solution was to rename the \pp directory to \pp20x or \pp211 and set the path variable to the location of the gnu libraries and fpc executables at the command prompt before launching a make from the source directory. Since make build always targets the \pp directory (unless you change the parameters.), fpc will always end in the \pp directory. Just be sure you keep fpc.cfg "safe" and put your working copy in \pp\bin\i386-win32 directory. I also had to maintain separate directories for the source of fpc. The only real drawback is that this eats a lot of disk space. Also, remember to change the source directories in the Lazarus environment.
Daniel
Alexandre Leclerc <[EMAIL PROTECTED]> wrote:
Alexandre Leclerc <[EMAIL PROTECTED]> wrote:
2006/5/13, Mattias Gaertner <[EMAIL PROTECTED]>:
> If you want to use two different lazarus with different setups, then start
> the second with
>
> /path/of/the/second/lazarus
> --primary-config-path=/home/username/.secondlazarus
>
> This way you can test new packages or new lazarus versions comfortably
> without poking in the files, that the IDE can automatically setup for you.
So since, unfortunately, installing a package required to statically
compile it in the current version of lazarus; with this trick I can
kick-start another more recent version of lazarus that does not have
the components yet statically compiled in it? (And it will still work
in the design time tools?)
When I tested that (replacing the exe with another one) this did not
worked quite well...
--
Alexandre Leclerc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
Blab-away for as little as 1ยข/min. Make PC-to-Phone Calls using Yahoo! Messenger with Voice.
