xcode github

We do general Unix development on Mac OS X but because some of the libaries we link against are currently on 32 bit we have to produce 32 bit binaries.When using Xcode 6 we can debug Unix binaries by selecting My Mac (32-bit) in the scheme selector, on Xcode 7 we only get My Mac and it gives the error: the specified architecture 'x86_64' is not compatible with 'i386-apple-macosx' in '/usr/atc-5.00.5/dev/cust0400/xcust'.I don't see any method of specifying i386 or 32-bit anywhere in build settings.Thanks, regards, Rob.

It seems that the console log for XC7 misses a lot of data. If an app writes say 100 lines to NSLOG, only a subset will appear in console. Prior to 10.11 and XC7, this was never an issue.

help me! whith xcode 6.3

error: unexpectedly found nil while unwrapping an Optional valuehiyas I for the life of me can not see whats wrong with the following codexim a noob to swift so thats probbably why 🙂I been stuck in this for so ling and if you can spot the propbem it be a real saver for me.it seems to work or at least show on the xcode viewer but errors on the real phone.many many thanksBrianimport UIKitimport CoreMotionclass ViewController: UIViewController { let motionManager = CMMotionManager() override func viewDidLoad() { if motionManager.gyroAvailable { motionManager.deviceMotionUpdateInterval = 0.2; motionManager.gyroUpdateInterval = 0.2 motionManager.startDeviceMotionUpdates() motionManager.startGyroUpdatesToQueue(NSOperationQueue.currentQueue()) { [weak self] (gyroData: CMGyroData!, error: NSError!) in if error != nil { println((error)) } self!.outputRotationData(gyroData.rotationRate) } } else { / } super.viewDidLoad() } func outputRotationData(rotation:CMRotationRate) { var attitude = CMAttitude() var moti

Hi,I'm using xcode 7 beta and iOS 9 beta.Upon running the app on device using xcode, sometimes app is stuck on launch image.I'm receving these log on xcode. Can some help me about this messages.Thanks

I believe that at one time, it was mentioned that when Swift would reach 2.0 (or later?), its standard library would no longer be included in the app bundle as the Swift language would have stabilized enough to have a system-wide version available. In Xcode 7 beta 1 though, the libSwiftCore etc are still built into the app bundle.Now I was wondering when we can expect the Swift standard library to not be included any longer in the app bundle. Is there any time table available?And concerning App Thinning, might this process be smart enough to strip the Swift libraries from the binary sent to the device at install time?

Hi,are there any new requirements for background location tracking in iOS9?Got problems with my new walking app on iOS9 devices:Tracking starts normal in foreground, but if I switch the app to the background the location updates and also the time tracker stops until the app is switched back to foreground. This happens only on my iOS9 test device. Same project is running fine in the background on iOS8 devices and also running fine on the iOS9 simulator.Also the project is running fine when I am compiling the project with xcode 6.3.2 against iOS8.As always when I got such issues, I have created a simple test app which is logging time and distance in the log, this test app reproduces the issue.The test app can be downloaded as a zip at this url: www.ihanwel.com/export/test.zipAny idea? Maybe someone has some time to compile my test app and check it on the own device. Thanks.Cheers,Hanno

Hi,An other member of my team (Organization) published an archive on itunes connect, via Xcode (For TestFlight). After 2-3 days, he can show crashes on Xcode Organizer.But my xcode show anything. We have both itunes account with Admin role.Can I show the crashes without building archives ? Any maners to see crashes, or is just in the Xcode of the person who build ?ThanksEdit : I have an account for Member Center and another email for iTunes connect, should be the reason ?

Say I'd like to write a generic function dotProduct, something like:func dotProduct<T: FixedSizeArrayType where T.Element: BasicArithmeticType>(a: T, b: T) -> T.Element { var sum = T(0) for i in 0 ..< T.Count { sum = sum + a[i] * b[i] } return sum }This is just some haphazard pseudo code meant to illustrate the requirements for the function:It takes as arguments two fixed size arrays of equal length and element type and returns the dot product of the two arguments (the type of the return value is of course the same as the element type of the two arguments). It's also ok to make it as a method, with self replacing the first arg.I want compile time errors if I try to call it with arguments of different size/count/length or element type, and if I try to receive a return value of some other type than the element type of the two arguments.And as can be seen, The T.Element type should conform to an imaginary BasicArithmeticType protocol. This protocol is possible to write yourself, but currentl

Hi all,In XCode 7, when I enabled Swift optimization for my target, I am getting EXC_BAD_INSTRUCTION exceptions where there were none if compiled by XCode 6.3.Unfortunately, nothing is printed on the Console when it happens, and the address sanitizer or Zombies find nothing.Is anybody else seeing this?So far I cannot make a clear and small reproducible case (smaller than the whole project) in order to file a bug.

In 10.11, I can't build anything in xCode. It just hangs on the Signing product step. This is with the newest xCode 7 beta as well as version 6.3.2.Any ideas?