The libSDL files are copied from the prebuilt directory at prebuilt/darwin-x86/sdl/lib/ and then ranlib is run against them after the copy and appears to strip the architecture information which then leads to the linking error. To show this you can compile up the master branch until the libSDL error, then run;
cp prebuilt/darwin-x86/sdl/lib/libSDL* out/host/darwin-x86/obj/STATIC_LIBRARIES/libSDL_intermediates/
then start make again and you get a similar error for the next library on (emulator-libelff.a).
An initial fix might be to stop ranlib running after the copy, which is pretty simple to do with the following patch in the build project;
diff --git a/core/combo/HOST_darwin-x86.mk b/core/combo/HOST_darwin-x86.mk
index 544a29e..407c74f 100644
--- a/core/combo/HOST_darwin-x86.mk
+++ b/core/combo/HOST_darwin-x86.mk
@@ -53,7 +53,11 @@ HOST_JNILIB_SUFFIX := .jnilib
HOST_GLOBAL_CFLAGS += \
-include $(call select-android-config-h,darwin-x86)
-HOST_RUN_RANLIB_AFTER_COPYING := true
+ifneq ($(filter 10.7.%, $(build_mac_version)),)
+ HOST_RUN_RANLIB_AFTER_COPYING := false
+else
+ HOST_RUN_RANLIB_AFTER_COPYING := true
+endif
HOST_GLOBAL_ARFLAGS := cqs
HOST_CUSTOM_LD_COMMAND := true
This stops the ranlib if the compilation host is 10.7, and so solves the libSDL issue.
So what are peoples thoughts about this as a first step?
Al
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
JBQ
> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Are you able to say if there are any plans to move the master emulator to a 64-build?, if so I'll focus on that rather than trying to get everything going through as 32 bit.
Al.
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
JBQ
Al.
--
T: @alsutton W: www.funkyandroid.com
The views expressed in this email are those of the author and not necessarily those of Funky Android Limited, it's associates, or it's subsidiaries.
JBQ