Re: [ooc-compiler] Package creation

[Michael v. A. <Mic...@de...>]

"fusionfive" <fus...@sp...> writes:

> Hi,
> 
> What are the basic steps when working with oo2c version 2.1.1? I can't find
> any tutorial.
> 
> Let's say I will start working on a project comprising two source files,
> `Main.Mod' and `Test.Mod', where `Main.Mod' uses the module `Test.Mod'. If I
> got it right I start by choosing a working directory, say `test' and then
> create a subfolder named `src' where `Main.Mod' and `Test.Mod' are located.
> In order to compile the program I then run the command
> 
>     oo2c -M -r .. Main.Mod
> 
> from `test/src'. Now the compiled program can be found in
> `test/bin'.

The usual setup is to call 

  oo2c -M Main.Mod

from the working directory `test'.  This gets you the same result as
you describe above, since the repository `-r .' is included in the
search path by default.

> Some of the options of oo2c require a package name as
> e.g. `--build-pkg-doc'. As far as I know a package is defined in a
> file named pkginfo.xml. What is the format of that file?

Packages come into play if you want to distribute source archives to
other people, which in turn install the library or program into the
oo2c setup.  The "pkg" commands are usually triggered from a Makefile,
which in turn is provided with parameters from an autoconf-generated
configure script.

There is no documentation on the format of the pkginfo.xml file.
There are lots of examples of its use, though.  You might take a look
at the files included in the oo2c tarball, or existing libraries like

  http://cvs.sourceforge.net/viewcvs.py/ooc/libicu-2.4/
  http://cvs.sourceforge.net/viewcvs.py/ooc/libpobj/
  http://cvs.sourceforge.net/viewcvs.py/visualoberon/X11/
  http://cvs.sourceforge.net/viewcvs.py/visualoberon/VisualOberon/

-- mva