Am 29.10.13 21:52, schrieb Clemens Lang:
On Tue, Oct 29, 2013 at 08:47:29PM +, Paul Bennett wrote:
Is 'xcode-select --install' really necessary on Mavericks?
Without xcode-select --install, /usr/lib/tclConfig.sh does not exist and
MacPorts base currently fails to configure
In article
,
Mark Anderson wrote:
> Will xcode-select --install work right without XCode.app? I do OSX and Mac
> Dev, so I always have it, but I'm curious to try now.
Yes.
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.9
BuildVersion: 13A598
$ ls -l /Applications/X
Will xcode-select --install work right without XCode.app? I do OSX and Mac
Dev, so I always have it, but I'm curious to try now.
—Mark
___
Mark E. Anderson
On Wed, Oct 30, 2013 at 7:52 PM, Ned Deily wrote:
> In article ,
> Paul Bennett wrote:
>
> > O
In article ,
Paul Bennett wrote:
> On 30 Oct 2013, at 23:04, Ned Deily wrote:
> > In article <52711f90.70...@macports.org>,
> > Rainer Muller wrote:
> >> Well, after thinking about this again, we could also do it the other way
> >> around. The majority of ports already builds just fine if you
On 30 Oct 2013, at 23:04, Ned Deily wrote:
> In article <52711f90.70...@macports.org>,
> Rainer Muller wrote:
>> Well, after thinking about this again, we could also do it the other way
>> around. The majority of ports already builds just fine if you have the
>> Command Line Tools only, without X
about
> missing xcodebuild, it's not actually required in this case).
>
> That would allow to save the additional installation of Xcode.app and
> only require `xcode-select --install`. However, with only ~2.5 GiB, the
> reduced disk usage without Xcode.app is quite small
On 2013-10-29 23:34, Ned Deily wrote:
> In article <50ac6a3d-a11c-4215-ad99-a4b61312f...@angellane.org>,
> Paul Bennett wrote:
>
>> Is 'xcode-select --install' really necessary on Mavericks?
>>
>> I propose that it isn't, and we should consider
In article <50ac6a3d-a11c-4215-ad99-a4b61312f...@angellane.org>,
Paul Bennett wrote:
> Is 'xcode-select --install' really necessary on Mavericks?
>
> I propose that it isn't, and we should consider a port that fails to build
> without as a bug.
>
>
On 2013-10-29 22:54, Paul Bennett wrote:
> On 29 Oct 2013, at 20:52, Clemens Lang wrote:
>
>> On Tue, Oct 29, 2013 at 08:47:29PM +, Paul Bennett wrote:
>>> Is 'xcode-select --install' really necessary on Mavericks?
>>
>> Without xcode-select --in
On 2013-10-29 21:47, Paul Bennett wrote:
> Xcode 5 installs command-line shims for the toolchain. These invoke the
> relevant actual tools in the SDK directories. So it's possible to install
> many (most?) ports without 'xcode-select --install'. What that command do
On 29 Oct 2013, at 20:52, Clemens Lang wrote:
> On Tue, Oct 29, 2013 at 08:47:29PM +, Paul Bennett wrote:
>> Is 'xcode-select --install' really necessary on Mavericks?
>
> Without xcode-select --install, /usr/lib/tclConfig.sh does not exist and
> MacPorts base
On Tue, Oct 29, 2013 at 08:47:29PM +, Paul Bennett wrote:
> Is 'xcode-select --install' really necessary on Mavericks?
Without xcode-select --install, /usr/lib/tclConfig.sh does not exist and
MacPorts base currently fails to configure because it cannot find Tcl.
We could discu
Is 'xcode-select --install' really necessary on Mavericks?
I propose that it isn't, and we should consider a port that fails to build
without as a bug.
Why?
Xcode 5 installs command-line shims for the toolchain. These invoke the
relevant actual tools in the SDK directories. S
In article <691f79eb-9f8d-4211-8608-cc833a1f2...@macports.org>,
Bradley Giesbrecht
wrote:
> Does xcode-select change the command line tools?
>
> If not, is there a command to issue after xcode-select to install the command
> line tools for the select xcode?
xcode-selec
Does xcode-select change the command line tools?
If not, is there a command to issue after xcode-select to install the command
line tools for the select xcode?
Regards,
Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
On Tue, May 29, 2012 at 09:47:30PM +0200, Marin Saric wrote:
> 2) If not, give /Applications/Xcode.app a try, run xcode-select
> -switch and issue a warning.
Automagically modifying a user's setting is not a good idea. MacPorts
should at most warn and tell the user what to do.
Doesn
manually run
xcode-select -switch /Applications/Xcode.app
before building MacPorts would work. The xcode-select defaulted to
non-existing "/Developer"
Suggestions:
1) Verify that xcode-select points to a sane path.
2) If not, give /Applications/Xcode.app a try, run xcode-select -switch a
Greetings,
I was just browsing the archive of the irc discussion where you
discovered that the reason some people had an xcode-select 2003
version instead of the latest 2307, was because they installed Xcode
4.2.1 *after* having updated to 10.7.3 (and you reference that at
https
On Fri, Feb 17, 2012 at 02:45:23PM -0800, James Berry wrote:
> (1) Do these tools exist on a machine if Xcode has never been
> installed? (i.e., are they part of the core os?)
Yes -- it looks like they are installed by the 10.7.3 update.
Dan
--
Dan R. K. Ports MIT CSAIL
ommand Line Tools installer, etc).
>
> So if that is indeed the case, I have a question about some of the tools of
> Xcode that are installed in /usr/bin: xcodebuild, xcode-select, xcrun, etc.
>
> My questions are these:
>
> (1) Do these tools exist on a machine if X
ave a question some of the tools of Xcode
that are installed in /usr/bin: xcodebuild, xcode-select, xcrun, etc.
My questions are these:
(1) Do these tools exist on a machine if Xcode has never been
installed? (i.e., are they part of the core os?)
(2) Are these tools installed when
21 matches
Mail list logo
