HaikuPorts
  • Login
  • Preferences
  • Help/Guide
  • Wiki
  • Timeline
  • Roadmap
  • View Tickets
  • Search
  • Port Log
  • Blog
wiki:WikiStart

Context Navigation

  • ← Previous Version
  • View Latest Version
  • Next Version →

Version 45 (modified by michaelvoliveira, 5 years ago) (diff)

Link organization on an index table with TOC macro.. got a rid from news page for a momment.. it will be back.. Additioned install instructions on the front page

Useful Pages

  1. Join HaikuPorts
  2. To Do
  3. Subversion Repository
  4. Guidelines
    1. Merging
    2. The PortLog
    3. Platforms
    4. Layout
  5. Mailing Lists
  6. HaikuPorter
    1. Introduction
    2. Requirements
    3. Usage
  7. Installation
  8. Finding a Directory's Path
    1. Terminal
    2. Shell Script
    3. Makefile
    4. C
    5. C++
    6. Python
  9. Common Porting Problems
    1. Main UNIX differences
    2. Missing functions
    3. Compile time problems
    4. GCC 2 build problems
    5. GCC 4 build problems
    6. Haiku fixed problems
  10. Porting Tips
    1. Documentation
    2. Places to check
    3. Getting started on Haiku
      1. gcc 2.x (default)
      2. gcc 4.x
      3. gcc 2.x and 4.x hybrid
    4. Porting considerations
    5. Preparing for distribution
    6. Providing Distributions
    7. Using CMake
    8. Directories
    1. Library Versions
  12. Create the Patch
    1. Cleaning your patch
  13. Adding Ports

Welcome to HaikuPorts

HaikuPorts is a centralized collection of software ported to the  Haiku platform. Each port contains the Haiku-specific patches to the original source code. Along with a Subversion repository to store all patches, this Trac site eases cooperation on porting efforts. There is also a mailing list for the discussion of the project. The haikuporter tool is provided to ease the fetching, patching and building of source code.

Objective

The main objective of the HaikuPorts project is to centralize ports of software to the Haiku platform. This avoids reinvention of the wheel when the person that ported an older version of a software package didn't provide a patch and seems to have disappeared from the face of the earth.

More importantly, solutions to problems faced when porting one application may be valuable when porting another. For this purpose, the PortLog, Trac tickets and the CommonProblems page can be consulted when facing problems. To make this work, some Guidelines should be followed.

Haikuporter can be compared to a slim version of  Gentoo Portage. It fetches the original source code, applies the Haiku-specific patches, builds, and optionally installs the port. This package management aspect, however, is by no means the essence of the HaikuPorts project.

Platforms

Haiku has many API advantages over BeOS and Zeta, which includes but is not limited to better POSIX compatibility. These API advantages greatly improves the ease of porting software to Haiku. Due to this, it is unreasonable to expect software that compiles on Haiku to compile on BeOS or Zeta without additional effort. While BeOS R5, BONE, and Zeta are still of importance, focus has shifted to Haiku.

Getting Started

To install the HaikuPorts system on your Haiku, type on your terminal: 

chmod 755 installhaikuporter.sh
./installhaikuporter.sh

For information about installation, see Installation. To know how to add a HaikuPort to the tree, see AddingPorts. Don't forget to read the Guidelines! Milestone M1 lists a set of the most common/important software packages. It is recommended (recent versions of) these are ported first.

Downloads

Looking for pre-built binaries? Check our  Downloads page. For a complete collection, check for LibPak

Download in other formats:

  • Plain Text
Trac Powered

Powered by Trac 0.13dev-r10686
By Edgewall Software.

Visit the Trac open source project at
http://trac.edgewall.org/