Jonas Maebe schrieb:
ppudump probably does not depend on cpubase in trunk. cpubase is part
of the code generator, and therefore the ppu loading should in fact
not depend on it (directly nor indirectly).
That looks like the right explanation.
Consequently the code generation has to be separate
On 31 Aug 2010, at 21:00, Hans-Peter Diettrich wrote:
> D:/repos/fpc-2.5.trunk/compiler/ppc386.exe -Ur -Xs -O2 -n -Fu..
> -FuD:/repos/fpc-2.5.trunk/rtl/units/i386-win32 -FE. -FUunits/i386-win32
> -di386 -dRELEASE ppudump.pp -Fu../i386 -Fi..
>
> I cannot see any -Fu../x86 here, so how can x86/c
Jonas Maebe schrieb:
The -FU (note the capital U) parameter specifies where the compiled
units are stored (-FUx86_64/units/x86_64-win64). If you have .o and .ppu
files in the x86 directory, you put them there yourself somehow (either
on the command line or by modifying the default Lazarus proj
On 31 Aug 2010, at 00:45, Hans-Peter Diettrich wrote:
Jonas Maebe schrieb:
D:/repos/NoGlobals/compiler/ppc2.exe -Fux86_64 -Fusystems -Fu../
rtl/units/x86_64-win64 -Fix86_64 -FE. -FUx86_64/units/x86_64-
win64 -dx86_64 -dGDB -dBROWSERLOG -Fux86 pp.pas
in contrast too a later
D:/repos/NoGlo
