[Vm-dev] Confused by FFI at Mac & Cog
estebanlm at gmail.com
Mon Dec 27 18:16:53 UTC 2010
I discovered that a similar problem happens also in the I32ABI plugin sources, the file ppc32abicc.c (which, by name, shouldn't be present in my compilations) is in fact required and works (afaik) properly.
Perhaps the name is just a "legacy name"? Perhaps you have the same kind of problem?
El 27/12/2010, a las 12:20p.m., Igor Stasenko escribió:
> I am trying to figure out, how to build FFI plugin on macs for cog vm.
> the platforms/Mac\ OS/plugins/SqueakFFIPrims contains following files:
> something tells me that i don't need to compile ppc* files, because
> Cog doesn't works on that arch anyways..
> so, i tried to use
> and failed.. then tried to use
> and it fails to compile with same error(s):
> /platforms/Mac OS/plugins/SqueakFFIPrims/x86-sysv-MacIntel.c:127:
> error: ‘FFICallTypeCDecl’ undeclared (first use in this function)
> /platforms/Mac OS/plugins/SqueakFFIPrims/x86-sysv-MacIntel.c:128:
> error: ‘FFICallTypeApi’ undeclared (first use in this function)
> These constants are defined only in FFIConstants shared pool.. and
> somehow they should be made available to
> these .c files..
> But our beloved VMMaker's code generator don't generating headers
> which can be included by other .c files,
> and all class var constants are just printed inside a body of
> generated .c file , like SqueakFFIPrims.c
> which means that these constants should be defined externally manually
> So, it seems like FFI is broken for Mac+Cog.
> P.S. Eliot's default .xcodeproj for FFI plugin are not builds because
> its not including one of the files above, which making a build
> complete (otherwise you got undefined symbols).
> Please shed a light, if FFI for Mac + Cog were in working state at
> some day? Or i doing something completely wrong?
> Of course i can disable it from build and forget about it, since we
> have new stuff coming (of course if Santa decide that we were good
> but still..
> Best regards,
> Igor Stasenko AKA sig.
More information about the Vm-dev