Ticket #594 (closed roadmap: done)

Opened 5 years ago

Last modified 5 years ago

library distribution

Reported by: allison Owned by:
Priority: normal Milestone: 1.4
Component: install Version:
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

Develop a strategy for distributing/packaging/installing libraries outside the Parrot distribution. This may be as simple as:

- PIR libraries are installed in prefix/versiondir/library - C extensions are installed in prefix/versiondir/dynext - includes are installed in prefix/versiondir/include

It's worth thinking about whether we can provide some tools to make installation easier for library writers.

Change History

Changed 5 years ago by allison

  • component changed from none to install

Changed 5 years ago by allison

  • status changed from new to closed
  • resolution set to done

- PIR libraries are installed in: prefix/lib/versiondir/library (e.g. /usr/lib/parrot/1.4.0/library) - C extensions are installed in: prefix/lib/versiondir/dynext (e.g. /usr/lib/parrot/1.4.0/dynext) - PIR/PASM includes are installed in: prefix/lib/versiondir/include (e.g. /usr/lib/parrot/1.4.0/include)

These install locations are documented in PDD 30.

Since installation of libraries consists of copying the files into a particular directory, additional tools aren't really necessary. (If a specific need for tools comes up later, we can develop them then.)

That leaves packaging/distribution. Added comments to PDD 30 on the subject in r40146.

Note: See TracTickets for help on using tickets.