+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Development (/forumdisplay.php?fid=32)
+--- Forum: Feature Suggestions (/forumdisplay.php?fid=9)
+--- Thread: [LINUX] XBMC for Linux port to ARM architecture CPU and SoC chips? (/showthread.php?tid=35139)
- McGeagh - 2009-03-31 18:44
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
- spiff - 2009-03-31 19:07
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)
- davilla - 2009-03-31 19:09
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.
- McGeagh - 2009-04-01 15:21
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
- spiff - 2009-04-01 15:49
edit Makefile.in not Makefile. voila
- davilla - 2009-04-01 17:34
As the dev who brought XBMC for Mac in-line with the make files, I highly recommend concentrating on getting configure/make working. If you don't understand the build process, then you should start there. XBMC is highly dependent on configure/make and hacking things into place is only going to get frustrating.
- McGeagh - 2009-04-03 11:49
I fucked up somewhere somehow!
Basically, I installed a load of dependency packages that the linker was moaning about, then did a clean/distclean and a configure... now when i make, it fails immediately, erroring on a realloc!
I tried installing libc and gcc and other stuff, but nothing worked... so decided to start again...
Noticed a few things have changed in the latest svn, and again a few issues regarding --disable-gl
you guys really dont like me using SDL instead of GL do you! lol.
The reason for this post is... do I bother highlighting the aspects that dont work when using --disable-gl, or is it a lost cause for you lot and i shouldnt bother bugging you about it?
- spiff - 2009-04-03 12:52
all reports are appreciated
- davilla - 2009-04-03 16:09
McGeagh Wrote:I fucked up somewhere somehow!
Basically, I installed a load of dependency packages that the linker was moaning about, then did a clean/distclean and a configure... now when i make, it fails immediately, erroring on a realloc!
I tried installing libc and gcc and other stuff, but nothing worked... so decided to start again...
Noticed a few things have changed in the latest svn, and again a few issues regarding --disable-gl
you guys really dont like me using SDL instead of GL do you! lol.
The reason for this post is... do I bother highlighting the aspects that dont work when using --disable-gl, or is it a lost cause for you lot and i shouldnt bother bugging you about it?
If make barfs trying to realloc a huge chunk of memory, your make is too old. "make --version" and post the version.
- althekiller - 2009-04-03 17:32
spiff Wrote:all reports are appreciated
Even more so in patch form.