Hello,
I added wince support to internal linker.
Please try it and see if all works fine.
Use -Xi compiler option to enable internal linker.
Yury Sidorov.

Mailing lists / fpc-devel / 2006-05
7 messages · 3 people · –
Reply by email Subscribe to this list Your subscription
Read-only archive. Use j and k to move between messages.
Hello,
I added wince support to internal linker.
Please try it and see if all works fine.
Use -Xi compiler option to enable internal linker.
Yury Sidorov.
Good job, now the internal assembler :)
From: "Florian Klaempfl"
Thanks :)
Internal assembler is a complex task. And I think it is not very critical for wince now, because internal linker does not require libpXXX.a files for smartlinking. Without smartlink libs generation external assembler is fast enough...
Yury Sidorov.
Correct me if I am wrong, but having an internal assembler (and a internal linker) means you don't need to have arm-wince binutils to cross compile to arm-wince anymore.
This would simplify distribution of a Lazarus add-on that would package everything needed for creating arm-wince programs on win32. Nevertheless adding the binutils to the package is not a big deal.
Vincent.
From: "Florian Klaempfl" Thanks :) Internal assembler is a complex task. And I think it…
Well, the a draft and a infrastrucure is already here, see aasmcpu.pas and armins.dat in the arm dir :)
Correct me if I am wrong, but having an internal assembler (and a internal linker) means…
From: "Vincent Snijders"
Sure, internal assembler is very very good :)
I did not look at current state of arm internal writer yet. Florian started to do it some time ago, but abandoned. Florian, what need to be done to finish it? Is it very complex?
Adapting internal linker for wince was not really solved all problems relatively quickly, but I was stuck and was almost crazy trying to find out how to calculate correct absolute relocs for arm object files :)
Yury.
No, it's only some work, see other mail. The dat file is from a port of nasm (the x86 fpc assembler is based on nasm) to arm but it's buggy and needs to be updated, luckily enough the arm doesn't have that much instructions as x86 :)
Yes, I know this from win64: you one case and two others break ;)