Thank you for sharing the solution. I have to admit that the ARM build
happened faster than I thought it will. Regarding rdtsc() - in fact, you
may return 42, but the proper function would be great. As the header
name says - it is only for execution time measurements and it is not
critical for the application operation. By the way - did not you have
any problems with OpenGL?
Kind regards,
Orson
On 11/25/2013 05:21 PM, Robert Yates wrote:
Two problems to fix in order to allow compiling for ARM.
The first was to add the proper "Boost::Context assembly wrapper" files
for ARM, and modify common/system/fcontext.s to include them. The files
'jump_arm_aapcs_elf_gas.S' and 'make_arm_aapcs_elf_gas.S' I acquired
from the boost_1_55_0.tar.bz2 download from http://www.boost.org/
The second parch is for a fake rdtsc() function in include/profile.h to
make the compiler happy. I'm not a c++ programmer so I don't actually
know what the right thing to do is, but I'm sure returning the number
'42' isn't it. ;-) There seems to be a cycle counter register built
into ARM CPUs similar to the TSC register in x86 CPUs, but reading it is
not trivial just google 'arm cycle counter' to see what I mean.
But with these two patches I'm able to compile under Arch linux ARM on
my Chromebook
(http://archlinuxarm.org/platforms/armv7/samsung/samsung-chromebook) and
it seems to be running well.
Both patches are against revision 4499 of the lp:kicad branch.
_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp