Do not use the MACOs packagemaker package. Using iceberg saves your effort and effort. How to Use the iceberg packaging Tool

For Mac development, we often need to package to generate the installation file. Naturally, we will use packagemaker, which comes with Mac and is recommended by xcode, unfortunately, this packagemake is neither intelligent nor human-friendly. As a result, many new users are frequently blocked when using packagemaker, and the official tutorial has only one article, there is no good solution to the problem. The most important thing is that after packagemaker is used, it is difficult to manage the version of the packaged file (pmdoc) and finally let me give up.

After constantly searching, I finally found a better packaging tool, iceberg. I recommend it to you, especially new users, and advise you not to use packagemaker, it will only upset you.

: Http://s.sudre.free.fr/Software/files/Iceberg.dmg

Tutorial: http://s.sudre.free.fr/Software/documentation/Iceberg/English.lproj/documentation/index.html

The tutorial is detailed. I will not elaborate on how to install it. If you have any questions, please leave a message and I will give you a patient answer, note the following points:

1. We recommend using iceberg to create mpkg instead of PKG, because mpkg is easier to manage.

2. If the file installation path is not in the default path, you must first create the path successfully, set the current path to default destination, and then use the add files function;

3. If you want to integrate the PKG of the generated components into a file of mpkg, install it in/contents/resources.

In addition, I mainly want to compare packagemaker and iceberg so that you can make the right choice:

(1) is the guide comprehensive?

Packagemaker:Relatively small, not detailed. There is an official Article: packagemaker User Guide

Iceberg:Relatively comprehensive, iceberg User Guide

(2) Is modularity supported?

Packagemaker:It cannot be modularized. You can only package all files into one PKG at a time, which is very difficult to manage multi-version and multi-module.

Iceberg:Modularization is supported. You can divide the file to be packaged into small components, which component is needed, and which component is compiled. The advantage is that, if different modules or new functions are available in each version, you don't need to worry about whether or not to release files.

(3) Can version management be performed on packaged files?

Packagemaker:Version Management is not involved, because the XML file in pmdoc is a huge one. If you modify one, all entries will be modified. Of course, you can manually update the XML file tidy after each version.

Iceberg:RatioPackagemakerBetter, because of the branch, and because of the iceberg components function, it makes version management very easy.

(3) are crash or inexplicable problems frequently occurring?

Packagemaker:I often crash here, and there may be a problem that caused me to crash: I did not select File A, but after PKG is installed, there is a file a, and it crashed for a day, later, I gave up.

Iceberg:It took a while, not to encounter crash or strange problems.

(4) which one is more powerful?

Packagemaker:The basic packaging function is supported. For example, if I want to add a background image or something, it cannot be implemented.

Iceberg:In addition to supporting the basic packaging function, there are some other highlights. This is useful only after you have tried it.

Please indicate the source of original article loading: http://blog.csdn.net/handsomerocco/