[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 277
  • Last Modified:

Installation software

For Windows we have many installation-maker software -- from huge commercial InstallShield to free InnoSetup.
What about Mac? How you create installation package from compiled software?
  • 2
1 Solution
Nearly all simple-to-moderately complex Mac OS X applications are self-contained:
all executable code, shared libraries (bundles or frameworks), localizable resources,
etc. are encapsulated within a directory with specific format and a .app filename
extension (an application wrapper).  This allows the user to perform simple drag-n-drop
installations - dragging the app by its icon and dropping it on the destination folder,
typically /Applications or ~/Applications.  These self-contained apps make installation
(and removal) trivial.

However some applications require more complex installations:
Components might need to be installed in specific places, for instance fonts and
frameworks that are used by other applications, system utilities, services and
daemons (startup items).   Some installations may require scripts to run pre- or post-
install.  These are usually done using the Mac OS X built-in Installer application.
(Unlike Windows, Mac OS X has a built-in Installer app - good news for developers -
bad news for third party installer companies like installshield).  The Apple developer
tools contain an app called "PackageMaker" to help you build Installer packages:


App bundles and Installer packages are both directory trees containing many files.
For distribution purposes, it is often convenient to package all the files in a compressed
archive.  In the Windows world, .ZIP archives are commonly used.  Mac OS X understands
.ZIP archives, but it is not commonly used under Mac OS X.  Smaller installations may
use the more Unix-traditional .tar.gz compression packaging (which will be automatically
expanded by the Finder, when downloaded).  However, most OS X savvy apps are distributed
on compressed disk image files (.dmg) which are easily createable:


Korsar_13Author Commented:
Thanks for your answer.

One more question: currently our company porting some Photoshop plug-ins from Windows to Mac.
Under Windows, system registry checking allows us to find applications  already installed (Photoshop, Photoshop Elements, PaintShopPro, PhotoPaint etc), so that we can install our plug-ins into these applications.

How can I find out  what applications are  installed on Mac and  where the information is kept?
Although Apple has standardized many things with Mac OS X, plug-in management does not
appear to be one of them.

Many of the newer Mac OS X specific apps don't store the plug-ins in the application wrapper.
That makes it more difficult to upgrade or re-install the app without damaging or losing the
extensions.  For instance Apple apps store store plug-ins in plug-in directories in /Library or

Although I do not have Photoshop installed, it apparently stores plug-ins within the application
directory.   This convention probably carries over from the Classic MacOS (along with the file
naming conventions used here: http://www.adobe.com/support/downloads/detail.jsp?ftpID=1878 )

You can use the 'locate'  or  'find'  command to find installed software.  Again, I don't have
photoshop installed (so I don't know the exact installed filename), but it would be something
like this:
      locate "*/Adobe Photoshop CS.app"
The locate command allows rudimentary filename globbing, but not full regular expressions.
You may have to use awk, sort, uniq, etc to clean up the output.


Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now