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 52 (modified by passick, 2 years ago) (diff)

Added link to the WritingBepFile article

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
  11. Writing BepFile
    1. BepFile name
    2. How HaikuPorter works
    3. Writing BepFile
    4. License file
    5. Patch file
    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. Haiku has many API advantages over BeOS and Zeta, which includes but is not limited to better POSIX compatibility. The main goal of this site is to facilitate cooperation towards porting efforts.

News

  • HaikuPorts is moving to BitBucket  -- Posted on 2013-04-27 09:58 : author augiedoggie
  • Haiku R1 Alpha 4.1 Released  -- Posted on 2012-11-16 13:30 : author scottmc
  • Haiku R1 Alpha 2 released  -- Posted on 2010-05-11 06:05 : author mmadia

The HaikuPorter

The HaikuPorter tool is provided to ease the fetching, patching and building of source code. It can be compared to a slim version of  Gentoo Portage. Each port contains the Haiku-specific patches to the original source code. 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.

Get Started

  • Ports checkout: svn co http://ports.haiku-files.org/svn/haikuports
  • Install the HaikuPorts system on your Haiku:
    wget http://ports.haiku-files.org/svn/haikuporter/trunk/installhaikuporter.sh -O- -q | sh -
    
  •  Download ports and run it on your own system. For a complete collection, check for LibPak

Get Involved

  • The HaikuPorts mailing list is the community forum.
  • Join us! be a member and start hacking the ports.

Documentation

For information about installation, see Installation. To know how to add a HaikuPort to the tree, see AddingPorts. To make this work, some Guidelines should be followed. The Roadmap lists a set of the most common/important software packages. It is recommended (recent versions of) these are ported first.

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.

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/