Rony, I don't think there is a problem with that. For example there is the GUI Application 'PackageMaker', and there is the command line program 'packagemaker' I have written some scripts to create packages from the Makefile. See: platform/unix/macosx/MakeRexxPackage
I think from my current point of view, it would be easier to have the Makefile execute a single script, that would intern execute separate scripts for the different phases of creating the distribution package. Bruce On Feb 9, 2011, at 3:26 AM, Rony G. Flatscher wrote: > Although there are Apple GUI-based utilities the students have the task > to create the bundles "by hand", such that that process can be Makefile > controlled. The links you supply are great, because they lead one quite > directly to the spots where Apple talks about their file system > structures and what goes with what (though there is additional knowledge > needed). > > The task for the students to make everything "batchable" is to make the > creation of MacOSX bundles independent of any third party tools (even > from Apple), which will allow eventually everyone on a Mac to create the > bundles from the command line interface without a need to first delve > into whatever GUI-based tools there are and to learn their logic how to > operate the GUIs first (which may take precious time away). > > Besides, in the end it is astonishing to see how little one needs to do, > if one knows what one does... > :) > > As the students write up a seminar paper on the BSF4ooRexx installation > for MacOSX and a Bachelor thesis on BSF4ooRexx installers for Windows, > Linux and MacOSX (here including ooRexx with BSF4ooRexx itself), all > their research efforts and experiments should be available for anyone > who is interested in this area of development. (It will take a little > while though, before these are done.) > > ---rony > > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
