[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Do we expect GNUmed to require makefiles to be run on the
From: |
James Busser |
Subject: |
[Gnumed-devel] Do we expect GNUmed to require makefiles to be run on the Mac? |
Date: |
Fri, 21 Aug 2009 13:50:39 -0700 |
Is it fair to surmise that – with the exception where the Mac may
lack or lag behind in ports of dependencies – there is nothing about
GNUmed that should require (re) compiling on the Mac?
The answer may be relevant to setting up – on a Mac, in "Xcode Tools"
– the various dependencies and other build requirements, into a
single directory that can then be bundled as the Mac client.
===========================================
Building Makefile Projects With Xcode
MacOSX-native applications can be built in a number of environments.
Most UNIX utilities are built using makefiles, though some are built
using build scripts, imakefiles, or various other mechanisms.
If you are porting a UNIX command-line tool for personal use, you
probably want to continue using the
existing build environment, because keeping multiple build
environments synchronized can be tricky at best.
However if you are porting a more extensive tool and you plan to add
a MacOSXGUI to the tool, you may
find it more convenient to work with the project in a development
environment such as Xcode.
Note: These instructions apply to the latest version of Xcode.
Although Xcode keeps track of build settings in its own preferences
files for information beyond what could
normally be maintained in a makefile, it can also work closely with
your project’s makefiles. If you want to
use Xcode for development in Mac OS X, you can include a makefile in
a Xcode project (instructions...).
- [Gnumed-devel] Do we expect GNUmed to require makefiles to be run on the Mac?,
James Busser <=