User Tools

Site Tools


porting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
porting [2011/09/30 08:02]
192.89.97.1
porting [2011/09/30 08:08] (current)
192.89.97.1
Line 4: Line 4:
  
   * Lack of memory protection.   * Lack of memory protection.
-  * Filesystem ​paths+ 
 +=== Non-ixemul software === 
 + 
 +When porting non-ixemul software check file system ​paths and path handling. Often *nix path handling is used what is incompatible with Amiga path handling.
  
 ===== Porting from Linux ===== ===== Porting from Linux =====
Line 15: Line 18:
  
  * Setting up GeekGadgets  * Setting up GeekGadgets
 +
 +=== MorphOS ===
 +
 +MorphOS SDK provides GeekGadgets development environment including Bash port and required build tools (automake etc.). To port software you usually start by running configure script from MorphOS shell and then executing make.
  
 ==== Fixing the makefiles ==== ==== Fixing the makefiles ====
Line 26: Line 33:
 ==== pthreads ==== ==== pthreads ====
  
-AOS4 has a partial(?) pthread implementation. For older AOS, and for AROS (what about MorphOS?​) ​you need to wrap the Amiga specific calls yourself (is this correct?)+AOS4 has a partial(?) pthread implementation. For older AOS, and for AROS you need to wrap the Amiga specific calls yourself (is this correct?). MorphOS provides pthreads implementation but using native Amiga API is recommended as pthreads can not be securely implemented on Amiga.
  
 ==== AmiCygnix ==== ==== AmiCygnix ====
porting.1317369754.txt.gz · Last modified: 2011/09/30 08:02 by 192.89.97.1