> Same here: installing XCode and opening it once seems to install command line
> tools. At least they are listed in Preferences as installed (at the same path
> as XCode.app).
> Seems as if no separate install is required with 12.x anymore.
I’m agreeing with Ryan here.
Opening Xcode 12.2 did
On 16/11/2020 02:56, Lothar Haeger wrote:
Same here: installing XCode and opening it once seems to install command line
tools. At least they are listed in Preferences as installed (at the same path
as XCode.app).
Seems as if no separate install is required with 12.x anymore.
Am 16.11.2020 um
I have a PR here to update the QLColorCode port
https://github.com/macports/macports-ports/pull/9138 and while
everything builds, the highlight functionality of this does not work.
One observation: /opt/local/lib/liblua.dylib (port: lua) was installed
with permissions 0644. I have since fixed
> On 16. Nov 2020, at 09:28, Ken Cunningham
> wrote:
>
>> Same here: installing XCode and opening it once seems to install command
>> line tools. At least they are listed in Preferences as installed (at the
>> same path as XCode.app).
>> Seems as if no separate install is required with 12.x
> On 16. Nov 2020, at 10:05, Wahlstedt Jyrki wrote:
>
>
>
>> Dominik Reichardt mailto:domi...@gmail.com>> kirjoitti
>> 16.11.2020 kello 10.55:
>>
>> In Xcode itself I actually do not see the CLT listed at all, only the
>> simulators.
>>
> I have mine here:
>
>
Indeed, there it is, than
On Nov 16, 2020, at 02:40, Andrew Udvare wrote:
> I have a PR here to update the QLColorCode port
> https://github.com/macports/macports-ports/pull/9138 and while everything
> builds, the highlight functionality of this does not work.
>
> One observation: /opt/local/lib/liblua.dylib (port: l
On Nov 16, 2020, at 02:55, Dominik Reichardt wrote:
> Yes, everyone replying that you have the CLT installed, check if it’s
> actually the correct one. Because apparently there is a bug that makes Xcode
> report that the CLTs are installed *without* checking whether it is the
> correct versi
On 16/11/2020 11:45, Ryan Schmidt wrote:
You get this error when doing what?
This happens when I try to load a preview.
1. Load Finder
2. Pick a file that would load a preview with it like a shell script
that ends with .sh
3. Use the space-bar to trigger a full preview with Quick Look
Compa
On Nov 16, 2020, at 13:17, Andrew Udvare wrote:
> On 16/11/2020 11:45, Ryan Schmidt wrote:
>> You get this error when doing what?
>
> This happens when I try to load a preview.
>
> 1. Load Finder
> 2. Pick a file that would load a preview with it like a shell script that
> ends with .sh
> 3.
On 16/11/2020 14:30, Ryan Schmidt wrote:
On Nov 16, 2020, at 13:17, Andrew Udvare wrote:
On 16/11/2020 11:45, Ryan Schmidt wrote:
You get this error when doing what?
This happens when I try to load a preview.
1. Load Finder
2. Pick a file that would load a preview with it like a shell scr
Apart from the Xcode problem (which I'm working on); thanks Ryan and the
rest for your work.
-- Dave
On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt
wrote:
> You should definitely never run with a mismatched set of Xcode and its
> command line tools. Either update the command line tools to the Xcode
> 12.2 version or downgrade Xcode to whatever it was before. Using Xcode
> 11.x and match
Hi Ryan!
Ryan Schmidt wrote:
So I have to force the "gcc-4.2" of xcode... that one works (and, luckily,
libxml2 still compiles with it)
My point is that "sudo port upgrade outdated" should work. If it does not, we
may have a bug somewhere that we need to fix, and what you're describing above
On Nov 16, 2020, at 17:58, Riccardo Mottola wrote:
>
> Ryan Schmidt wrote:
>>> So I have to force the "gcc-4.2" of xcode... that one works (and, luckily,
>>> libxml2 still compiles with it)
>> My point is that "sudo port upgrade outdated" should work. If it does not,
>> we may have a bug some
On Nov 16, 2020, at 17:32, raf wrote:
> On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote:
>
>> You should definitely never run with a mismatched set of Xcode and its
>> command line tools. Either update the command line tools to the Xcode
>> 12.2 version or downgrade Xcode to whatever
On Mon, Nov 16, 2020 at 06:45:17PM -0600, Ryan Schmidt
wrote:
> On Nov 16, 2020, at 17:32, raf wrote:
>
> > On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote:
> >
> >> You should definitely never run with a mismatched set of Xcode and its
> >> command line tools. Either update the c
16 matches
Mail list logo
