- #List installed macports mac os x
- #List installed macports install
- #List installed macports update
- #List installed macports upgrade
Installing these with sudo port install should give you the dependencies you'll need to build the frameworks and applications, though some applications may have more dependencies of course.
#List installed macports upgrade
Upgrade all installed packages and uninstall the old versions: Upgrade all outdated packages with new versions and uninstall the old versions:
Switch to a different installed version of a package: Upgrade a package and uninstall the old version (omit the -u to just disable the old version, useful when the new version may break things, note however that keeping the old version around may confuse the KDE build): List all installed packages with available updates: List the contents of an installed package To enable a parallel build, which is encouraged, define the number `N` of processes Install a package, the -v is needed to see the build output: List all available packages, this will be very long:
#List installed macports update
Update MacPorts and the list of available ports, you should do this first whenever you work with the port command: MacPorts should be very easy to use for anyone used to Linux-style package management. It is recommended to initially install MacPorts using the package installer as this will automatically set-up your required $PATH. This enables you to control the environment search hierarchy for different purposes.Īpplications installed via MacPorts can be run from the command line or from the /Applications/MacPorts folder in the finder. MacPorts installs everything into /opt/local and so doesn't interfere with the base OS X install or any other local installs you have.
#List installed macports mac os x
"The MacPorts Project is an open-source community initiative to design an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the Mac OS X operating system." Once installed, perform an OS X Software Update to ensure your system is fully up-to-date and reboot if required. Snow Leopard and Leopard come with it installed by default. If you are running Tiger you will also need to install Apple's X11 from your OS X Install disks. Install Apple's XCode developer tools either from your OS X install disks or download from or install from the OSX App Store. You will be glad when you get Dolphin and Krusader installed :-) My pet hate is how useless Finder is for file management, particularly with hidden. It would appear all bash customisations need to go in ~/.profile rather than ~/.bashrc. The OS X filesystem, despite appearances, is by default not case sensitive, so KDE = kde = kDe.
One point to remember is that OS X is a customised version of BSD, so while it feels fairly familiar to a Linux developer, there are the occasional banana skins to slip you up. The main disadvantage is compiling all the MacPort dependencies takes longer than binary installs, but the ease of maintenance is worth it. It also gives you the choice of installing and running the latest stable KDE SC for everyday use while still developing on the unstable trunk. This approach has the big advantage of using MacPorts to build, install and keep updated the base system and libraries required with minimal effort and without touching the base OSX system install. It sets up a MacPorts installation to provide the required dependencies and uses this to then build a KDE kf5 development environment. The process described here is one of many ways to set up a KDE development environment on Mac OS X. 7 Configure your KDE development environment.6 Installing the base requirements for KDE4.5 Installing the base requirements for KDE Frameworks.
0 kommentar(er)
