Codesign assumes folder structure, fails.

Hi all, I’m getting an error from codesign when it tries to sign a third-party embedded framework. The error is: /Users/grahamcox/Library/Developer/Xcode/DerivedData/Drawkit-hlbdxcwqkoiqzlesbkfsrobctzke/Build/Products/Debug/Ortelius 2.app/Contents/Frameworks/GEOS.framework/Versions/A: No such

Re: awakeFromFetch behaviour change in 10.12?

On Mon, 25 Jul 2016 14:12:42 -0500, Kyle Sluder said: >On Mon, Jul 25, 2016, at 09:14 AM, Sean McBride wrote: >> Hi all, >> >> I'm observing that in 10.12 my awakeFromFetch methods are being called >> more than in 10.11 and earlier. Specifically, it's called more than once >> for an object

Re: NSFileHandle and thread safety

> As long as each thread has a separate file handle, they’re independent of > each other, since each file handle remembers its own offset in the file. Ah, durr, you’re right. Apologies, I once had the displeasure of debugging an ancient codebase that used the same Unix file descriptor with

Re: NSFileHandle and thread safety

> On Jul 25, 2016, at 12:37 PM, Daniel Stenmark wrote: > > 2. Can I read from a single file using two NSFileHandles on two threads at > the same time? > > Why would you need to do that in the first place? To get multithreaded access to the file contents. This is

Re: NSFileHandle and thread safety

> On 26 Jul 2016, at 5:37 AM, Daniel Stenmark wrote: > > 2. Can I read from a single file using two NSFileHandles on two threads at > the same time? > > Why would you need to do that in the first place? Unless you’re reading a > single byte at a time, it sounds like

Re: NSFileHandle and thread safety

1. Can I write to two different files using two NSFIleHandles from two threads at the same time? Yes. 2. Can I read from a single file using two NSFileHandles on two threads at the same time? Why would you need to do that in the first place? Unless you’re reading a single byte at a time, it

NSFileHandle and thread safety

Hello list, I find Apple’s documentation on this unclear. It says: "NSFileHandle, NSData, Cocoa streams: Most of the Foundation objects you use to read and write file data can be used from any single thread but should not be used from multiple threads simultaneously." For example I would

Re: awakeFromFetch behaviour change in 10.12?

On Mon, Jul 25, 2016, at 09:14 AM, Sean McBride wrote: > Hi all, > > I'm observing that in 10.12 my awakeFromFetch methods are being called > more than in 10.11 and earlier. Specifically, it's called more than once > for an object that's already been fetched previously. > > Perhaps I have

Re: kCFStreamPropertySSLSettingC

> On Jul 25, 2016, at 6:47 AM, Gerriet M. Denkmann wrote: > > What would be the right thing to choose? “Mac Developer” while you’re developing, I.e. for your regular build-and-run cycle. “Mac Distribution” is for Release builds you’re going to submit to the Mac App

awakeFromFetch behaviour change in 10.12?

Hi all, I'm observing that in 10.12 my awakeFromFetch methods are being called more than in 10.11 and earlier. Specifically, it's called more than once for an object that's already been fetched previously. Perhaps I have misunderstood the method's semantics all these years, but I expected

Re: kCFStreamPropertySSLSettingC

> On 25 Jul 2016, at 15:30, Alastair Houghton > wrote: > > >> On 23 Jul 2016, at 00:41, Jens Alfke wrote: >> >> >>> On Jul 22, 2016, at 2:46 AM, Gerriet M. Denkmann >>> wrote: >>> >>> When it gets some streams it

Re: kCFStreamPropertySSLSettings

> On 23 Jul 2016, at 00:41, Jens Alfke wrote: > > >> On Jul 22, 2016, at 2:46 AM, Gerriet M. Denkmann >> wrote: >> >> When it gets some streams it will show a panel: >> “MyApp wants to sign using key “something” in your keychain” / “Allow” “Deny” >