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 variableto the location of the gnu libraries and fpc executables at the command prompt before launchinga make from the source directory. Since make
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
On Fri, 12 May 2006 11:11:18 -0400
Alexandre Leclerc [EMAIL PROTECTED] wrote:
I installed vtv and worked nice. Laz recompiled itself.
I use an independent tree for svn version that I compile and use and
if all works well I move to my usual working lazarus tree.
Now I see that the vtv
I installed vtv and worked nice. Laz recompiled itself.
I use an independent tree for svn version that I compile and use and
if all works well I move to my usual working lazarus tree.
Now I see that the vtv component is not included in the compilation of
laz from svn. I did:
- copied vtv folder
