I just upgraded to 2.0.17 and now any bundle that uses pre-compiled binaries in Bundle Support bundle fails to load due to the incompatible architectures:
> /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require': dlopen(/Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle, 9): no suitable image found. Did find: (LoadError)
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: no matching architecture in universal wrapper
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: no matching architecture in universal wrapper - /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle
> from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> from /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/textmate.rb:4:in `<top (required)>'
> from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> from /Users/christos/Library/Application Support/TextMate/Bundles/Linter.tmbundle/Support/lib/linter.rb:1:in `<top (required)>'
> from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> from /Users/christos/.rbenv/versions/2.7.2/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
> from Lint/Strip/Ensure on Save:2:in `<main>'
I checked and the builds don't contain arm_64 architectures:
> [~]> file "/Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle"
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle: Mach-O universal binary with 3 architectures: [ppc_7400:Mach-O bundle ppc_7400] [i386:Mach-O bundle i386] [x86_64:Mach-O 64-bit bundle x86_64]
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture ppc7400): Mach-O bundle ppc_7400
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture i386): Mach-O bundle i386
> /Users/christos/Library/Application Support/TextMate/Managed/Bundles/Bundle Support.tmbundle/Support/shared/lib/osx/plist.bundle (for architecture x86_64): Mach-O 64-bit bundle x86_64
I can't even find the source for those binaries to try and build them. Any ideas?
On 25 May 2021, at 16:28, Roberto Avanzi wrote:
> So, to summarize:
>
> - The /opt/homebrew is the new location for APple Silicon based macs
> - On macos 11.00 the default behaviour of ibtool seem to have changed,
> since I made no specific change to default configuration myself
> - For two nib's the directory is still created, and there seems to be
> a big sur special version inside
It turns out the issue is with xib files that contain a custom view (no window), a table view, and which has a deployment target (presumably less than macOS 11), for those, ibtool will create a directory.
Hard to believe this is anything but a bug in latest Xcode, but as a workaround, I have now removed deployment target from all xib files.
Regarding `/opt/homebrew`: If you run `./configure` then it now creates a default `local.rave` containing:
add FLAGS "-I/usr/local/include"
add LN_FLAGS "-L/usr/local/lib"
Then it complains that it cannot find dependencies.
Edit `local.ninja` with your M1 homebrew paths and then re-run `./configure`, and it should hopefully work.
Personally I get build dependencies from nixpkgs, there are people who use MacPorts, and then there is non-M1 homebrew, so I think it is fair that if dependencies are not in `/usr/local` then the user will have to manually edit the file, because `./configure` can quickly become a mess if it has to try everything.
Hello
Already last december I was ablt to build TextMate on a M1 MacBook (I
shared this with Michael Sheets) but at the time and still now I
encounter some errors during the build. For instance
FAILED: /Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/GrammarProperties.nib
/bin/cp -Xp /Users/mocenigo/build/textmate/release/_CompileXib/Frameworks/BundleEditor/resources/English.lproj/GrammarProperties.nib
/Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/GrammarProperties.nib
&& touch /Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/GrammarProperties.nib
cp: /Users/mocenigo/build/textmate/release/_CompileXib/Frameworks/BundleEditor/resources/English.lproj/GrammarProperties.nib
is a directory (not copied).
ninja: build stopped: subcommand failed.
Now, if i continue to issue the command "ninja TextMate" it will
eventually build and sign a working application. But this should not
happen, I guess.
How can I set up the environment to just build properly, with "ninja
TextMate" and not stopping on the cp commands?
Roberto
Is there any change that I can set something like NSToolTipsFont ? I can set NSToolTipsFontSize via;
defaults write com.macromates.TextMate NSToolTipsFontSize 24
How can I set font-family for ToolTips?
Thanks
Uğur Özyılmazel
https://ugur.ozyilmazel.comhttps://github.com/vigo
Hello
I have been able to compile TextMate a few times already, but for some
reason I have to issue the command dozens of time because the build
often halts with errors like
[2/150] Copy ‘/Users/mocenigo/build/textmate/release/_CompileXi...BundleEditor/resources/English.lproj/FileDropProperties.nib’…
FAILED: /Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/FileDropProperties.nib
/bin/cp -Xp /Users/mocenigo/build/textmate/release/_CompileXib/Frameworks/BundleEditor/resources/English.lproj/FileDropProperties.nib
/Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/FileDropProperties.nib
&& touch /Users/mocenigo/build/textmate/release/Applications/TextMate/TextMate.app/Contents/Resources/English.lproj/FileDropProperties.nib
cp: /Users/mocenigo/build/textmate/release/_CompileXib/Frameworks/BundleEditor/resources/English.lproj/FileDropProperties.nib
is a directory (not copied).
but I am following the instructions on the github page to the letter.
What could this be and how do I fix it? It semes that t "-r"
(recursive) flag is missing or something from the cp command.
Roberto
