User forums > General (but related to Code::Blocks)

Compiling MAC OS X in Windows

<< < (2/2)

MortenMacFly:

--- Quote from: papricaz on May 22, 2011, 02:03:05 pm ---That's the issue. I'm not developing ONLY for Mac.

--- End quote ---
See, that's the issue we face with this project, too. actually licensing is even more strict: You are not even allowed to use e.g. XCode without a proper Mac hardware. You (as we) have no other choice for serious Mac development than to buy Mac hardware and use a remote desktop tool or alike. Luckily there is C::B for the Mac and sharing resources (files) between platforms works. So the project settings are not an issue.

Also, virtualising is not an option, as you are not allowed to create a virtual machine for a Mac without a Mac... So, unless you buy a Mac you are going to run in circles therefore... ;-)

However, once you own a Mac there is Bootcamp / vmWare again which you could use to virtualise MS Windows (assuming you have a Windows license). Then (and IMHO only then) you have both OS'es on one hardware.

...or is there anything I am missing?!

oBFusCATed:
papricaz: another problem is the Mac way of doing things is very different from the normal computing, so you'll need a continuous testing on the Mac, to verify that your software is working as expected. The best thing is to have a Mac dedicated developer, but I'm sure they are very rear creatures, because of this "Apply way", I mentioned earlier.

papricaz:
All this just makes me loss my interest in developing cross platform softwares... :(


--- Quote ---but I'm sure they are very rear creatures
--- End quote ---
Excuse me but my English is not that good. What's rear? Google Translate is not being smart

oBFusCATed:
Sorry, I meant RARE...

And yes, developing cross platform software is N times harder than single platform software. (N is the number of platforms)

Navigation

[0] Message Index

[*] Previous page