However, there are still a few problems exist, for eg. around paths as Nils said. But i'm happy with the current results. (... and waiting for offical snapshot... :)

Florian forgot to tell you that you must also define AMIGA when compiling the compiler, otherwise it will compile for the linux-m68k target by default (thats why there are path problems)...

The compiler defines to compile for AmigaOS (either cross or native): AMIGA
GDB
M68k

Good luck.

söndag 24 november 2002 12:51 skrev Carl Eric Codere:

Hi,
I think the problem with paths has something to do with fexpand, I will do some more test and try to compile a native amigacompiler on uae and see if the result is the same.

If I do a test like this

writeln(fexpand(paramstr(0)));
what I get both with crosslinux and native amiga is a path with win32 delimiter and a starting \ before the path.

Will do some more checking.

Nisse

From: Nils Sjöholm
To:
Subject: Re: [fpc-devel]Amiga68k Compilation options... Date sent: Sun, 24 Nov 2002 16:13:33 +0100
Send reply to:

I think the problem with paths has something to do with fexpand, I will do some more test and try to compile a native amigacompiler on uae and see if the result is the same.

Not really strange... ;-) There's IFDEF UNIX in fexpand.inc currently; if Amiga uses forward slashes _and_ doesn't define UNIX (which I suspect is true), it doesn't work correctly now. I'll correct it and let all you know afterwards (I can't test it on all platforms, of course, so it's possible I might break something).

Tomas

söndag 24 november 2002 12:51 skrev Carl Eric Codere:

Done some more tests and it's fexpand that cause the problem, I guess.

If I compile this testprog

program fexpandtest;
uses dos;
begin
   writeln(fexpand(paramstr(0));
end.

on native linux I get

/home/ninne/Harddrives/Applications/fpcnative/fexpandtest

compiled on uae with native amigacompiler I get

Dh1:fpcnative/DH1:FPCNATIVE/FEXPANDTEST

I get double paths plus uppercase.

Nisse

Hi,

Yes, i've figured out that Florian forgot this, so i added by myself to the make command he recommended. And then it worked. So the problems not resulted by this.

Same here. Because of this, the compiler also searches it's units and etc at wrong place. It's even a wonder it still works with files copied to that wrong place... :)

(And these problems not because UAE, since i'm testing it on a real machine.)

Bye,