Tag Info

Hot answers tagged

5

Until you can find an explicit statement from Apple saying the artwork is copyright free and suitable for public use assume it is copyright and do not distribute it. Ideally, contact Apple Developer Technical Support or Apple's legal department and ask them directly. Be careful of assuming a right to use Apple's artwork or images. Apple have previously ...


5

The Xcode license and your developer agreement are the two documents you should read carefully to be certain you understand your obligations, but Xcode is delivered to developers for the express purpose of making apps. Clearly, the graphic elements like buttons and standard API are permitted use - royalty free per the licensing term. This is covered in the ...


2

Symlinks are often destroyed by some archiving tools, especially by those built into some versions of PHP, for example. Try to pack and unpack an archive and check if symlinks are still alive. Also, symlinks won't be saved on NTFS or similar non-mac filesystem. Please check if symlinks get broken after you access the drive from Windows computer.


2

In order to compile multiple separate files (separate binaries as a result) You would need to create separate targets for every file. To add new target please choose: File -> New -> Target.., select for example Command Line Tool. Make sure it's properly added to Your project. Here's example: My main.cpp is added to target multiple_targets like this: My ...


2

What you are seeing are QuickLook preview thumbnails: if you look closely at your screenshot, you will notice each “icon” shows the start of the file’s content. You are correct this is due to you installing TextMate 2, which provides a powerful QuickLook extension for source code files (try selecting one of the files in Finder and hitting space). The ...


2

You need to start/open Xcode once to accept the license agreement. Easiest way to run the application is by clicking on the Spotlight icon on top right and just type its name.


1

My guess is that something else is at work. The warnings are that you don't have Xcode (i.e., developer tools) installed. Many MacPorts packages require compiling, so you need the build environment. It would really help to have the full crash window, because there are a lot of useful messages to developers. What follows is complete speculation from ...


1

Have a look at: Launching Your App on Devices


1

This error can happen if you renamed Xcode.app. I suggest you do the following: Quit Xcode.app, iOS Simulator.app, etc. Execute: sudo killall -9 com.apple.CoreSimulator.CoreSimulatorService Execute: rm -rf ~/Library/*/CoreSimulator Reboot and try again.


1

Probably the certificate is outdated. To circumvent this the following procedure should work: Open "System Preferences" Hit "Security & Privacy" Hit the tab "General" Click the lock and enter your admin password at "Allow applications from anywhere" mark the radio button "Anywhere" then click the button "Allow from anywhere" or like indicated in ...


1

For Wine under OS X I use Wine_1.7.36.dmg from "Wine.app Downloads" on kronenberg.org and XQuartz and both install and work nicely without the need to use MacPorts.


1

Use Product → Archive to create a binary of your app. Then go to the Organizer window and optionally validate it. Lastly, export the app to your desktop so you can distribute it as you wish.


1

This is a known bug. It was fixed on macports by removing -fforce-addr flag. Here's the fix. Remove this flag from configure file and repeat the operation. If You want to build for different architecture, pass params to configure. For example, to change arch to 64bit - on my machine I'll do: ./configure --target=x86_64-apple-darwin14.1.0 ...


1

Make sure you have something entered in Organization Name and Organization Identifier. Right now it can be any placeholder. I think it matters later on when you're submitting projects to the App Store.



Only top voted, non community-wiki answers of a minimum length are eligible