PPC Big endian .v. x86 Little endian apps

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Aaron Gray - 29 Apr 2008 11:01 GMT

I am porting Mozilla's SpiderMonkey to MacOSX. It has a cpu configuration
program which generates headers for the target machine and uses them in the
main build.

What I am stuck on is how to get the main build either to use these specific
headers one for each build, or better to have some mechanism that is
designed to deal with this specifically for XCode.

I laster want to use MacOSX'es Javascript interpreter but I have legacy
extensions on SpiderMonkey that I need for now, until I get them converted..

Many thanks in advance,

Aaron

Reply to this Message

Heath Raftery - 30 Apr 2008 03:39 GMT

In comp.sys.mac.programmer.help Aaron Gray <ang.usenet@gmail.com> wrote:

> I am porting Mozilla's SpiderMonkey to MacOSX. It has a cpu configuration
> program

Do you mean 'configure' or something else?

> which generates headers for the target machine and uses them in the
> main build.
>
> What I am stuck on is how to get the main build either to use these specific
> headers one for each build, or better to have some mechanism that is
> designed to deal with this specifically for XCode.

Might be worth checking out how XCode handles this in its normal builds.
It is pretty slick.

But that said, I know this has already been covered for SpiderMonkey.
I can't remember the details, but check out the SpiderMonkey mailing
list. I believe someone has posted an XCode project for both
architectures. I recently updated my app, which links to SpiderMonkey,
for Universal build, and once I looked up what had already been done,
my part was quite easy.

Signature

*--------------------------------------------------------*

*______________________________________m_('.')_m_________*

Reply to this Message

Aaron Gray - 30 Apr 2008 17:28 GMT

> In comp.sys.mac.programmer.help Aaron Gray <ang.usenet@gmail.com> wrote:
>> I am porting Mozilla's SpiderMonkey to MacOSX. It has a cpu configuration
>> program
>
> Do you mean 'configure' or something else?

No the CPU config program jscpucfg, basically gets big endian/little endian
settings and int sizes and writes a .h file to the command line for
redirection to jscpucfg.h.

>> which generates headers for the target machine and uses them in the
>> main build.
[quoted text clipped - 13 lines]
> for Universal build, and once I looked up what had already been done,
> my part was quite easy.

Yes Carbon has some functions for native to bigendian/little endian.
SpiderMonkey has structs that get defined differently on different
archetectures.

I will follow this lead up.

Thanks,

Aaron

Reply to this Message

Mac Forum / Programming / Mac Programming / April 2008

PPC Big endian .v. x86 Little endian apps