Posts: 166
Joined: Nov 2008
Reputation:
1
Another thing to consider is that unless your dev board is based on widely used architecture, you might also encounter problems with vendor toolchain, when the compiler would generates invalid machine code. Those are extremely hard to find, and good Assembler knowledge for the platform is usually necessary. We have encountered such things more than once during porting our software to various SPARC and MIPS-like boards, and it was never fun.
Posts: 178
Joined: Oct 2008
Reputation:
0
McGeagh
Team-XBMC ARM Developer
Posts: 178
I know - ive got ubuntu running on beagle.
Also, the processor supports opengl, but the drivers for it hasnt (or wasnt) released yet.
Ive not checked in a while, so those drivers may have been released by now.
Thanks for the input though.
Posts: 178
Joined: Oct 2008
Reputation:
0
McGeagh
Team-XBMC ARM Developer
Posts: 178
Thanks very much for the links.
I have scratchbox and currently in the process of cross compiling... but thats put on hold for now during xmas... will try keep u all updated of my progress!
Posts: 178
Joined: Oct 2008
Reputation:
0
McGeagh
Team-XBMC ARM Developer
Posts: 178
well then let me put it back on topic....
Ive began working on porting XBMC onto ARMv7 architecture.
Initially in scratchbox (a crosscompiler/emulator), then onto the beagleboard, then onto further more beefier hardware that will be released soon...
Ive successfully (i think) configured xbmc, and when i do make, it fails on a particular file due to there being assembly code in it (obv x86)...
The file in question is: XBMC\xbmc\cores\DllLoader\ldt_keeper.c (Line 132)
just thought id post my progress here, and perhaps someone is able to help with this. while i wait, i will be looking into x86 assembly and try understand what that chunk of assembler is trying to do... and perhaps recreate a C version.
Incase its relevant, the error i get when 'make' is... unknown register name eax in asm
Posts: 178
Joined: Oct 2008
Reputation:
0
McGeagh
Team-XBMC ARM Developer
Posts: 178
Ah, thanks! its all good now, (i believe - just commented it out as its unlikely to be used)
While im here, might as well mention a few things...
The screensavers stuff wont let ./configure run if u use the option --disable-gl
I know SDL is not exactly supported, and u all prefer us to use openGL, but i just thought --disable-gl would actually still work.... nvm. Im not interested in screensavers, so just ignored that whole part of xbmc.
Also, i think i may have found a bug...
XBMC/xbmc/Picture.cpp
line 223.... i believe it should be . not ->
as with a -> it fails to make, and . doesnt
And finally, Im getting errors now about XBMC/xbmc/lib/libPython/XBPythonDllFuncs.S e.g:
unrecognised symbol type ""
loads of these errors, linked to every line that has FUNCTION in that file...
Are those important? I dont wanna remove chunks without knowing what it does
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
those are again assembly files. you need to disable the entire python stuff at first i think (it's a substantial amount of work getting that working). also see the ppc thread in the dev forum.
that picture.cpp thing is definitely wrong, trac it please (i'm at work and will surely forget)
Posts: 11,582
Joined: Feb 2008
Reputation:
84
davilla
Retired-Team-XBMC Developer
Posts: 11,582
you might want to look at the usage of ppc and powerpc. There were additions to build XBMC for Mac on ppc and several of the same issues existed regarding XBPythonDllFuncs and DllLoader.
Posts: 178
Joined: Oct 2008
Reputation:
0
McGeagh
Team-XBMC ARM Developer
Posts: 178
2009-04-01, 15:21
(This post was last modified: 2009-04-01, 15:30 by McGeagh.)
Ive removed the python stuff as (as far as im aware) its only used for scripts... and as this is really just a... a proof of concept, if you will.... im not bothered with having scripts.
Its a bit annoying though as have to edit it out of the configure AND makefile... and everytime i do ./configure, i then have to remove it from the makefile again... nvm
My next issue is to do with the linker (undefined reference for some of the libs)... seems i may have missed a few dependency packages