Changes between Version 20 and Version 21 of PortingTips

Timestamp:

11/27/09 13:27:01 (6 years ago)

Author:

mmadia

Comment:

--

PortingTips

@@ -21 +21 @@
 to your {{{build/jam/UserBuildConfig}}} file. This sets up a development environment and unzips a small tree of ready-to-use binary tools onto your image, including a Haiku-specific gcc2, [wiki:dev-lang/perl Perl] and autotools. Other helpful packages are {{{OpenSSL}}} and the {{{Pe}}} text editor (which allows you to jump to the line of an error message) and {{{Firefox}}} (which allows you to copy-and-paste console output to our Wiki pages).
 
-Most software cannot handle {{{i586-pc-haiku}}} yet, so it is usually necessary to {{{configure}}} with {{{--build=i586-pc-beos}}}, or you can:
+Most software cannot handle {{{i586-pc-haiku}}} yet, so it is usually necessary to 
 {{{
  cp /boot/common/share/libtool/config/config.* .
@@ -44 +44 @@
 == Porting considerations ==
 
-To automatically patch software with the BePorter tool, source tarballs should be diff'ed (cf. CreatePatch).
+To automatically patch software with the HaikuPorter tool, source tarballs should be diff'ed (cf. CreatePatch).
 
 Most projects however use SCM/VCS software, including [wiki:dev-util/cvs CVS], [wiki:dev-util/subversion Subversion], [wiki:dev-util/git Git], [wiki:dev-util/mercurial Mercurial] and [wiki:dev-util/bzr Bazaar], and accept patches only against their latest (HEAD/trunk/master) development version. A possible strategy is:
@@ -53 +53 @@
 Doing so, you can easily track or revert your own changes, and this is the preferred format for submitting patches to the respective projects.
 
-Note that it is not easily automatable for BePorter though, but once accepted, future source tarballs promise to compile without patching.
+Note that it is not easily automatable for HaikuPorter though, but once accepted, future source tarballs promise to compile without patching.
 
 Also note that doing so may, depending on the project, result in more dependencies but might be easier to handle, for instance when modifying {{{configure.in}}} or {{{Makefile.am}}} instead of an Autoconf-generated {{{configure}}} or Automake-generated {{{Makefile}}}.