Oric computers >> Tape Tools
by Andre Majorel » Tue, 26 Apr 2005 07:06:23 GMT
n 2005-04-24, bob < XXXX@XXXXX.COM > wrote:
There's no general answer to that because it depends on several
factors.
Software that talks to hardware for which there's no established
standard API (USB, firewire, CD/DVD writers, audio, ...) cannot
be written portably. It will usually only compile on your
platform if the author has written the necessary code.
Some software does not access hardware but is tightly integrated
with some environment. For example, Linux software written for
Gnome or KDE is not likely to compile on Mac OS.
Virtually all GUI-type Unix applications use X. Apple provides
an X server (in the developer CD ?) and so does the Fink project
(http://fink.sf.net/).
Some software requires libraries which may not be present by
default on your OS. Commercial Unix systems come with Motif.
Linux systems come with GTK. Mac OS probably has neither out of
the box. Fink may help there.
Some software is inherently non-portable. Case in point,
Euphoric (and hence Xeuphoric) is written for an i386 CPU.
Some Unix software is not portable because it uses platform
specific extensions, sometimes for a good reason, sometimes
gratuitously.
Some software will not compile on your platform because your
platform has bugs or does not follow the standard. One project I
maintain compiles out of the box on Linux and all major Unix
flavours EXCEPT Mac OS because the Mac OS X linker has hang-ups
about initialising a char array with a string constant.
And finally, there are small differences that could easily be
overcome if the author knew about them. Most libre Unix software
these days is written by Linux or *BSD users and many of those
are not going to pay for a proprietary OS when they can have a
libre one for free. So they're often unaware of the portability
requirements for Mac OS. If told about Mac OS portability
issues, some of them will be happy to work with you
to solve them and some will just ignore you.
Executive summary : some do, some don't. If they don't, the fix
can be anything from a trivial one-line change to "impossible".
The first thing to do is to extract the contents of the
distribution archive. Put the distribution archive into your
home directory (normally /home/bob but Mac OS may differ). Open
a terminal and cd into your home directory by typing "cd". If
the distribution archive has a .tar.gz extension, type
tar xzvf niftyprogram-1.0.0.tar.gz
This will (usually) create a directory named niftyprogram-1.0.0
which containts the source.
If tar doesn't support the "z" option, try this instead:
gzip -d <niftyprogram-1.0.0.tar.gz | tar xvf -
If the distribution archive has a ".tar.bz2" extension, type
tar xjvf niftyprogram-1.0.0.tar.bz2
If tar doesn't like the "j" option, do
bzip2 -d <niftyprogram-1.0.0.tar.bz2 | tar xvf -
Once you have extracted the source, cd into the source directory
by typing
cd niftyprogram-1.0.0
and look at what you have:
ls -l
You will probably see a file named "README" or "INSTALL" or some
such which contains instructions. Roughly speaking you can
expect one of two things :
- the software uses GNU autoconf. In that case, there's a file
named "configure". Run it by typing
./configure
- it doesn't. There's probably a file named "Makefile". Open it
with your text editor of choice and make any necessary
changes. Be sure to save in Unix text format (lines ter