porting to mac?

[vtor67]

I looked around the website and couldnt find any information about how/what language PJ64 was written with. in 1.7, since your rewriting it, would it possible to build it for a mac also? if you open source 1.7, i could take a stab at building it for mac. Sorry if this is a bad suggestion, but I never saw this idea floating around the forums anywhere (i searched)

[rswedlow]

One thing that's been questioned was open-sourcing it for others to contribute, to which no approval is given. In private discussion between some members it was completely refused.
As for porting to other OSes, the developers don't care, to openly put things for them.

The public 1.4 source of Project64 was done in C, but 1.7 source files seem to now be done in C++. 1.4 was to be the end of the project while having a lot of what is unique to this emulator even today, so just a port of version 1.4 to Macintosh isn't so far off. Unfortunately these encouragements for any other version are not given.

You would prefer to port 1.6 over 1.7; 1.7 is just a beta predisposition. If it is released, its identity would be 2.0 for many improvements and fixes, but in its beta form many things are also broken. 1.4 would be a lot better to port than beta 1.7.

[MES Seele]

Why would you bother going through the trouble of porting it when Mac already has a program intended for just this purpose?

Seriously, just run the program through Crossover. I own both both a pc and mac and find that the mac runs it just as well if not better. (the adage 'if it's not broken, don't fix it' is fitting)

If you don't know how to set it up, there is a thread in the '1.7 issues' section where some decent instructions have been posted.

[primeoj]

cause you might not have cross over capabilities

[vtor67]

also, it costs $40.

does pj64 work with darwine?

[XFi6]

Originally Posted by Squall_Leonhart

are you going to write the intricate thread synching code required to maintain synchronisation between the RDP, RCP and RSP?