• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Leopard man pages
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Leopard man pages


  • Subject: Re: Leopard man pages
  • From: Jean-Daniel Dupas <email@hidden>
  • Date: Wed, 19 Mar 2008 09:44:47 +0100


Actually, I have both Xcode 2.5 and 3.0 installed, so I do have that folder, but I also have an /Xcode2.5/usr/share/man/ folder. It looks like they contain basically the same things, though. At any rate, if I understand things correctly, I think that the utilities installed with Leopard's "UNIX Development Support" package are the same ones installed with Xcode 3.0. If not, it seems like I want to use the man pages at /usr/share/man to go with the utilities at /usr/ bin et al anyway.

Xcode 2.5 does not install anything in /usr on Leopard, so the "UNIX Development Support" package effectively come form Xcode 3.0. In fact, this is a copy of what you can find in /Developer/usr, but some tools does not works properly if not install in /usr (like glibtool, and most of the autogen package). If you only works with Xcode IDE, it's not a problem, but if you plan to do UNIX dev using traditionnal cli, this package is almost require.



About the problem with old man pages. Xcode does not really like updates. The only reliable way to update it is to uninstall the current version, and install then new one, else there is always some minor issus like this one. So I don't know how to get a "full" Leopard state.

I think it's not just Xcode that doesn't like the updates; the Leopard upgrade affects my Unix development environment, even if I'm not using Xcode. So does the Xcode upgrade, for that matter. Although like I said, I'm not trying to do any actual Unix development. But the command-line tools are certainly handy, and in some cases (like modifying dynamic library loading paths), indispensable.


Thanks again,
Dan

The UNIX dev environment is a part of Xcode. Try to install OS X without Xcode, and you will miss a lots of command line tools (like make, gcc etc.).
Even header files in /usr/include come with Xcode.












_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: "Sherm Pendley" <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Jean-Daniel Dupas <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Graham J Lee <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Dan Korn <email@hidden>)
 >Re: Linking to third-party Frameworks and dylibs from a plug-in (From: Peter O'Gorman <email@hidden>)
 >Leopard man pages (From: Dan Korn <email@hidden>)
 >Re: Leopard man pages (From: Jonas Maebe <email@hidden>)
 >Re: Leopard man pages (From: Dan Korn <email@hidden>)

  • Prev by Date: linking to a static lib and *not* a dynamic lib when both are present
  • Next by Date: Re: Designating an iPhone for development
  • Previous by thread: Re: Leopard man pages
  • Next by thread: Re: Leopard man pages
  • Index(es):
    • Date
    • Thread