Jrubik 0.9.7 For Mac
I've been working on getting the Cocoa port of DeSmuME 0.9.7 working, and I think it's working nicely at this point. The changes to the main source files are very minor.
QtiPlot 0.9.7 - Graphing and analysis software for scientists and engineers. Download the latest versions of the best Mac apps at safe and trusted MacUpdate Download, install, or update QtiPlot for Mac from MacUpdate.
They were made to get desmume to compile. However, the changes to the cocoa source are more extensive. The majority of the work was code refactoring to make the cocoa source a little more maintainable. The detailed changes are noted in the change log. Note: These changes are based on the release_0_9_7 branch. I did this so that we can have a Mac version of DeSmuME available on the website. I've done everything you asked.
I've attached the new files to this post. Riccardom, It looks like I missed the GPU_osd_stub.cpp file in the Xcode project. I enabled it, and the compiler errors for osd went away. All the files where I #ifdef'd the osd out were reverted back to their originals.
Zeromus, I remade the patches and rolled them all together into one file. Sorry, I'm still trying to get the hang of creating patches. Before, I used the diff on OS X to create the patches. This time, I used TortoiseSVN in Windows.
Jrubik 0.9.7 For Mac
I hope the patch is to your liking. Let me clarify: The conflicting macro is not with the one from NDSSystem.cpp. The conflicting macro is the check() assertion macro defined in Apple's CoreFoundation framework, specifically in the AssertMacros.h file.
Unfortunately, this file must be included in the Cocoa port. I tried renaming the macro in NDSSystem.cpp just to test it, but there was still a compiler error at MMU.h:244 due to the macro conflict in AssertMacros.h. But doing the check->dmaCheck rename fixes the error. It is possible to simply #undef Apple's check() macro at the top of MMU.h so that things compile.
Jrubik 0.9.7 For Macbook Pro
This way, the check->dmaCheck rename wouldn't be necessary. However, I do think that doing the rename would be the more lasting solution. I've applied all the changes you should need outside cocoa/ to trunk, could you please double check and rediff with only the changes in cocoa please?
The changes in cocoa/sndOSX.h and cocoa/sndOSX.mm looks strange though, do you really need the #undef OBJ_C in.h, actually all the ifdef changes looks strange like this: +#ifndef DESMUME_COCOA #define OBJ_C +#endif and this +#ifdef DESMUME_COCOA +volatile bool execute = true; +#else volatile desmume_BOOL execute = true; +#endif both in nds_controls.mm. More on bool, i see you are using BOOL in other files.
YouTube By Click 2 2 81 + Crack [CracksNow. Aadu malayalam movie free download utorrent for mac. Toggle navigation.
So why all these discrepancies? We can remove the define in src/types.h if that is causing problems.
Tell me about it! Yeah, some of the code looked a bit weird when I saw it for the first time. But I'm a bit more familiar with it now, so I was able to clean up a bunch of the #ifdef stuff. There was a bunch of declarations in the XCode project that are used for various #ifdefs throughout the code. I moved these declarations to a separate prefix header file to remove the XCode dependency. The reason I threw in the #ifndefs around certain declarations (like OBJ_C) was because I was afraid of breaking something. But all of this has been taken care of.
About the usage of type BOOL. This is a declared type in Objective-C. The reason why it's used throughout the code is because Apple uses type BOOL quite extensively within the Cocoa framework. We shouldn't have to worry about this because the conflict is addressed in types.h:211. I uploaded the Cocoa only changes in cocoa_desmume_patches_c.zip.
I looked at the commit file, and I saw that the compile wasn't working with the 10.4 SDK under GCC 4.2. This is correct -- the 10.4 SDK only supports GCC 4.0.
But I'm surprised you had this issue, because I know I set the XCode project targets to all use the GCC 4.0 compiler. I'm wondering if the setting gets changed when a different user opens the project? Because the setting shouldn't change. So about r3981. The changes I made were meant for the 0_9_7 branch, so I'm sure the build will fail when using the trunk files. I actually have a separate XCode project for trunk to account for all of the file differences between 0_9_7 and trunk.