* ARM iOS using Xcode 4.2.1?
@ 2012-01-10 20:40 Bob Vandette
2012-01-23 18:39 ` Anthony Green
0 siblings, 1 reply; 2+ messages in thread
From: Bob Vandette @ 2012-01-10 20:40 UTC (permalink / raw)
To: libffi-discuss
Has anyone successfully ported the libffi library to work with Xcode 4.2.1 in order
to produce a library for ARM iOS 5.0 platforms?
I tried using the libffi-3.0.10 sources and it appears that the newer Xcode assembler is
incompatible with some of the directives in src/arm/sysv.S.
It's complaining about:
.vfp
.ifc
.size
Even after commenting these issues out, the ffi.c file doesn't compile due to a missing structure
member (trampoline_table_entry).
Bob Vandette
Oracle
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: ARM iOS using Xcode 4.2.1?
2012-01-10 20:40 ARM iOS using Xcode 4.2.1? Bob Vandette
@ 2012-01-23 18:39 ` Anthony Green
0 siblings, 0 replies; 2+ messages in thread
From: Anthony Green @ 2012-01-23 18:39 UTC (permalink / raw)
To: Bob Vandette; +Cc: libffi-discuss
On Tue, Jan 10, 2012 at 3:40 PM, Bob Vandette <bob.vandette@oracle.com> wrote:
>
> Has anyone successfully ported the libffi library to work with Xcode 4.2.1 in order
> to produce a library for ARM iOS 5.0 platforms?
Check out this fork...
http://github.com/jspahrsummers/libffi
...and let me know how it works.
Thanks,
AG
> I tried using the libffi-3.0.10 sources and it appears that the newer Xcode assembler is
> incompatible with some of the directives in src/arm/sysv.S.
>
> It's complaining about:
>
> .vfp
> .ifc
> .size
>
> Even after commenting these issues out, the ffi.c file doesn't compile due to a missing structure
> member (trampoline_table_entry).
>
> Bob Vandette
> Oracle
>
>
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-01-23 18:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-01-10 20:40 ARM iOS using Xcode 4.2.1? Bob Vandette
2012-01-23 18:39 ` Anthony Green
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).