On 2015-11-08 15:37, Tomas Hajny wrote:
> Alright, but the difference between build.sh and build.cmd is much bigger
> than the $fpctarget anyway
Oh yes I understand that. I didn't mean I share a build script between
platforms. Each platform has its own build script... I just showed the
Linux one a
On Sun, November 8, 2015 15:30, Graeme Geldenhuys wrote:
> On 2015-11-08 13:26, Tomas Hajny wrote:
.
.
> I wasn't doing cross-compilation. I have a build script for fpGUI that
> creates the unit output path (seeing that FPC doesn't create paths at
> compile time), then I compile the framework us
On 2015-11-08 13:26, Tomas Hajny wrote:
>
> Yes, it works as designed. The same happens with target GO32v2. The reason
> is that these targets may be used with 8.3-limited file system (the
> original FAT)
Wow, does anybody actually install OS/2 on a FAT filesystem? In all my
years of using OS/2,
On Sun, November 8, 2015 12:03, Graeme Geldenhuys wrote:
Hi Graeme,
.
.
> I have use the $fpctarget macro for unit output for years, and this
> works under Windows, Linux and FreeBSD.
>
> eg:
> -FU../lib/$fpctarget/
>
> The output is normally something like "../lib/i386-linux/" or
> "../lib/
