patspiper wrote:
On 22/08/13 19:36, Mark Morgan Lloyd wrote:
I've never seen any suggestion that this breaks backwards
compatibility, and if it does it should probably be raised as a bug-
at least so that it can be documented properly. In any event, as long
as fpc (etc.) knows what version
On 22/08/13 19:36, Mark Morgan Lloyd wrote:
I started off with a standard FPC binary installation circa 2.0, this
put the utilities in /usr/local/bin ** . Since then I've generally
built from source- in many cases I've had to since there wasn't an
up-to-date binary- and I've never had to expl
patspiper wrote:
On 22/08/13 16:23, Mark Morgan Lloyd wrote:
patspiper wrote:
When multiple FPC versions are used, the fpc binary and related
utilities are usually located in //bin, and
the compiler itself (ppcxxx) in /version>/lib/fpc/. The folders could be different than
these, but the poi
On 22/08/13 17:26, Henry Vermaak wrote:
On Thu, Aug 22, 2013 at 05:12:04PM +0300, patspiper wrote:
On 22/08/13 16:23, Mark Morgan Lloyd wrote:
I usually add a couple of symlinks in /usr/local/bin e.g. ppcsparc
-> ppcsparc-2.6.2 and ppcsparc-2.6.2 ->
/usr/local/lib/fpc/2.6.2/ppcsparc. The fpc bi
On Thu, Aug 22, 2013 at 05:12:04PM +0300, patspiper wrote:
> On 22/08/13 16:23, Mark Morgan Lloyd wrote:
> >I usually add a couple of symlinks in /usr/local/bin e.g. ppcsparc
> >-> ppcsparc-2.6.2 and ppcsparc-2.6.2 ->
> >/usr/local/lib/fpc/2.6.2/ppcsparc. The fpc binary will be the one
> >installed
On 22/08/13 16:23, Mark Morgan Lloyd wrote:
patspiper wrote:
When multiple FPC versions are used, the fpc binary and related
utilities are usually located in //bin, and
the compiler itself (ppcxxx) in /version>/lib/fpc/. The folders could be different than
these, but the point to note is that
On 22/08/13 15:59, Mattias Gaertner wrote:
On Thu, 22 Aug 2013 15:39:47 +0300
patspiper wrote:
[...]
* If the FPCVER macro does not appear in any of the 2 paths
( and )
then the fpc binary can be queried to set the FPCVER macro.
The FPCVer always comes from querying the compiler.
Right.
patspiper wrote:
When multiple FPC versions are used, the fpc binary and related
utilities are usually located in //bin, and the
compiler itself (ppcxxx) in //lib/fpc/version>. The folders could be different than these, but the point to
note is that there are 2 folders that rely on the fpc ver
On Thu, 22 Aug 2013 15:39:47 +0300
patspiper wrote:
>[...]
>* If the FPCVER macro does not appear in any of the 2 paths
> ( and )
> then the fpc binary can be queried to set the FPCVER macro.
The FPCVer always comes from querying the compiler.
Mattias
--
Hi,
The following applies at least to Linux, and should probably apply as
well to other OSes.
When multiple FPC versions are used, the fpc binary and related
utilities are usually located in //bin, and the
compiler itself (ppcxxx) in //lib/fpc/version>. The folders could be different than th
10 matches
Mail list logo
