Bearbin's Automated Builds
#81
Just back up again - the VPS it's hosted on is having a bit of instability.
Reply
Thanks given by:
#82
I've just found this: http://www.kitware.com/blog/home/post/426
It describes, step by step, how to make RasPi cross-compiling work on Linux. Perhaps you could use that to set up crosscompiling on a more powerful PC rather than using the actual Pi for the compilation.
Reply
Thanks given by:
#83
If you go for cross compiling the only system libraries we use are the dynamic loader(should by libdl) and libm.
Reply
Thanks given by:
#84
I'll look into it.
Reply
Thanks given by:
#85
Thanks for that guide. If any of you has a raspi can you test MCServer Linux-RasPi New please Smile
Reply
Thanks given by:
#86
Doesn't seem to be building

Well, now that's trouble - the build process needs one of the executables it built to actually generate the bindings.
Reply
Thanks given by:
#87
ah. That would seem to be a problemTongue

How do you think I could get around that?
Reply
Thanks given by:
#88
Copying a tolua executable from the machine-local builds could help, but CMake might want to overwrite it with a fresh compile nevertheless.
Is there a way to execute normal (not crosscompile) cmake for tolua and then the crosscompile one for MCS? Hm, but that will make it complain, you'd need separate configuration folders, which would defeat the purpose of reusing the tolua executable. Dunno. Sorry.
Reply
Thanks given by:
#89
Cmake does have something on the wiki about it. I'm trying to decipher it now. It seems xoft that your right about compiling twice.
Looks like you have to do a build on the native platform then the crosscompiled platform and you can set the cmake file up to use the native version of the generator.
Reply
Thanks given by:
#90
I may have finally fixed the issues with Hard and Soft float. I have now created a hardfloat build (should improve performance) and I've also renamed the softfloat build.
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)