Hi,
I have had an issue building TextMate from the GitHub source for some time. I get the codesign error “resource fork, Finder information, or similar detritus not allowed” (introduced by Apple to enable notarization) for Dialog2.tmplugin:
Ians-MacBook-Pro:textmate ian$ ninja TextMate [5/116] Sign ‘build/PlugIns/dialog/Dialog2.tmplugin’… FAILED: build/PlugIns/dialog/Dialog2.tmplugin/Contents/_CodeSignature/CodeResources xcrun codesign --options runtime --timestamp -fs "-" build/PlugIns/dialog/Dialog2.tmplugin && touch build/PlugIns/dialog/Dialog2.tmplugin/Contents/_CodeSignature/CodeResources build/PlugIns/dialog/Dialog2.tmplugin: resource fork, Finder information, or similar detritus not allowed [6/116] Sign ‘build/PlugIns/dialog-1.x/Dialog.tmplugin’… build/PlugIns/dialog-1.x/Dialog.tmplugin: replacing existing signature [10/116] Compile ‘Frameworks/FileBro...src/FileBrowserDiskOperations.mm’… ninja: build stopped: subcommand failed. Ians-MacBook-Pro:textmate ian$
I assume this happens for others, too, on a fresh clone → configure → build? If not, then any pointers as to what detritus Dialog2.tmplugin might have would be appreciated.
Ian
On 31 Aug 2020, at 22:10, Ian Gregory via TextMate wrote:
Hi,
I have had an issue building TextMate from the GitHub source for some time. I get the codesign error “resource fork, Finder information, or similar detritus not allowed” (introduced by Apple to enable notarization) for Dialog2.tmplugin:
See this technical note: https://developer.apple.com/library/archive/qa/qa1940/_index.html
Basically one of the files in the build folder has “Finder info” or similar. You can either try to track down the file, as outlined in the technote, or maybe just delete the Dialog2.tmplugin build folder, however, the extended attribute may have been added to one of the resource files that are being copied to the build folder, so you may have to clear it from there.
-
Allan Odgaard -
Ian Gregory