I just wrote an application for submission to the app store - and I'm reading on forums that using a font that is not included on a users machine will cause the whole app to crash. I used a font called Handwriting - Dakota, and I never installed it so I'm not 100% sure if it comes with Mac by default. Does anyone else running Mac 10.6 have this font?? Any feedback would be greatly appreciated!
Best,
Zach
I've a clean (no non-developer apps) Mac OS X 10.6 (Snow Leopard) install and this font isn't present. Additionally, it's not listed on the Wikipedia "List of typefaces included with Mac OS X" article either.
At a guess, it's most likely installed by iLife, iWork or similar.
Related
last 2 years I am working primary on Macbook Pro with Snow Leopard system and in the following days I want to upgrade to Lion OS X system.
My worries comes from the setup that I currently use on the laptop - I have there installed and configured Ruby, Php, PostgreSQL, MySQL, Heroku-data, etc.
Then also Mail.app (over 12k emails), documents, photo galeries, just everything...
Is there any way to just install the new OS X and preserve my current programs+data+developer tools?
If not, could you give me any tips, how to make the upgrade painless as much as possible?
Up to now, I am not experienced in upgrading OSX system, so I will welcome all advices.
Thank you!
An OS upgrade on a Mac preserves all your files. The only thing to go with Lion are any PowerPC-dependent apps, as Rosetta is no longer available in 10.7.
There is a thread here:
How to Install and run a XulRunner Application on Mac OS X?
...in which a user mentions having trouble uninstalling XULRunner 7 so he could then install XULRunner 6. Unfortunately he just says he figured it out, but doesn't say how. It appears that I cannot private-message or email that user (CIRK).
So, does anyone know how one removes it, or at least get OS X to allow the install of XULRunner 6?
As a side-note, removing the /Library/Frameworks/XUL.framework directory does not work.
Thanks in advance.
Answering my own question a day later...
It appears that the XULRunner 7 installer not only adds files to the /Library/Frameworks folder, but also adds to /private
Specifically, I had to manually delete...
/private/var/db/receipts/org.mozilla.xulrunner.bom
/private/var/db/receipts/org.mozilla.xulrunner.plist
...along with removing the /Library/Frameworks/XUL.framework folder.
Hopefully that will be helpful to someone else.
edit: This is specifically relevant to OSX 10.6.7, reported to work on 10.7.2 as well
On Mac OS X 10.5.8 there is nothing under /private/... but there is a folder /Library/Receipts/xulrunner-*.mac.pkg which have to be removed too
This question already has answers here:
How can I develop for iPhone using a Windows development machine?
(42 answers)
Closed 5 years ago.
I am currently designing and planning an app that I intend to release for iPhone and iPad. I don't currently have a Mac, so I really have no way to actually publish the app, but I don't really want to buy a Mac either just for the development of the app.
Is there any way that I can write (and maybe even test) the app on Windows, then, once I have a finished product, buy a Mac or borrow a friends Mac to publish it.
I know that there is no way to publish to the Apple App Store without a Mac, but I was wondering if there is a way that I could develop and test the app (in Objective-C) on Windows.
I was wondering if there is a way that I could develop and test the app (in Objective-C) on Windows.
No, there is not. XCode is required for iOS development, and it is only available on Mac OS.
You could get a second, cheap hard drive, and install OS X on the hard drive to make your computer into a Hackintosh. You'd need a copy of OS X, and a willingness to break the TOS for the operating system.
This is actually a very frequently asked question, and I'm afraid the answer is no, you cannot do iOS development on Windows.
Back in the iPhone OS 2.0 days there was a cross-compiling framework that did accomplish this but it's abandoned and doesn't work for years now and AFAIK nobody bothered to make it work again (it's a lot of work and requires intimate knowledge about cross-compiling and hunts a constantly moving target).
The usual recommendation is to buy a used Mac Mini since they're cheaply available on sites like eBay.
duskwuff is right to a point... XCode itself is not actually requred in fact there is IDEA's AppCode IDE. Unfortunately, that only runs on OS X. The best thing you can do (other than get a cheap Mac) is install GCC on windows or a Linux VM compile from the command line, as GCC can compile Objective-C. However, that still is not a good solution since you won't have Access to Cocoa Touch and all those calls will error out as undefined or undeclared....
No, you can't. If your going to buy a Mac to publish in the future, why not just buy it now?
You can use OS X in a virtual machine on your windows system. I have read few articles on the internet how to do it using VirtualBox for that (google for it). Even if it's not officially supported by VirtualBox, it's possible. This breaks the TOC for OS X, and you need to buy a copy as well, but VirtualBox is free.
Yes you can!!!
Use virtual box.
Search some guides on "lifehacker.com" about getting mac on virtual box.
It's what I always used before getting a mac.
am using Os X 10.6.4 and X code Version 3.2.3 for developing some simple app files and using PackageMaker to distribute these app files. But when trying to run the package on some other mac I am getting error that the package is not compatible with the Os X its running and file would not be installed. Is this a problem with X code or package maker. sorry for reposting it but although I tried changing base SDK to 10.5, it was getting compiled and ran well on mac I am using for development (Mac OS X 10.6.4) but when installed on mac running OS X 10.5 the .app files were grayed out and message poped up saying 'you cannot use this version of application with this version of Mac'. Any idea why is this happening? Also as mentioned earlier I am using IBOutlet for accepting user date from form and then writing that into a text file. Any idea or solution about it?
Do you have anything set in your Info.plist for the LSMinimumSystemVersion key? This is one place the system looks.
When I was brand new I had trouble figuring this out...
Make sure that your Base SDK and deployment target are 10.5 and that you have the right compiler on(GCG4.0/4.2), also make sure that when you change these settings you change it for both Release and Debug, I once made this mistake of changing it only on debug, and when I built for release it only worked on 10.6 because I didn't change those settings.
I know that MAC OS X 10.5 comes with Apache installed but I would like to install the latest Apache without touching the OS Defaults incase it causes problems in the future with other udpates. So I have used the details located at: http://diymacserver.com/installing-apache/compiling-apache-on-leopard/ But I'm unsure how to make this the 64 Bit version of Apache as it seems to still install the 32 bit version.
Any help is appreciated
Cheers
Add this to your ~/.bash_profile which means that your architecture is 64-bit ant you’d like to compile Universal binaries.
export CFLAGS="-arch x86_64"
This page claims that a flag for gcc (maix64) should do the trick. Give it a whirl, and if you need any more help, post back here.
Be aware that you may run into issues with your apache modules. If they are compiled in 32-bit mode, then you will not be able to load them into a 64-bit apache.
I had this issue with mod_python, took a bit of thinking to figure out this was the reason.
Don't export CFLAGS from your .bash_profile or any other dot file. Your home directory could live on for decades, the system you're currently using is transient.
There's a guide on Apple's web site, Porting UNIX/Linux Applications to Mac OS X, that talks specifically about how to make autoconf and make and other similar build systems fit into the Mac OS X Universal Binary scheme. If you're going to build cross-Unix applications on Mac OS X, you need to read and understand this guide.
That said, I strongly question why you want to build Apache 64-bit. Just because Leopard can run 64-bit software doesn't mean you want all software on your system to be 64-bit. (It's not Linux.) In fact, virtually none of the software that ships with Leopard runs 64-bit by default, and most of the applications included with Leopard only ship 32-bit.
Unless you have a pressing need to run Apache 64-bit, I wouldn't bother trying to build it that way.
If you would have read a bit further on the same site there is some information on compiling Apache in 64 bits mode!
http://diymacserver.com/2008/10/04/update-on-64-bits-compilation/