curl/packages
John E. Malmberg 1c44f83e54 build_vms.com: use existing curlbuild.h and parsing fix
This patch removes building curlbuild.h from the build_vms.com procedure
and uses the one in the daily or release tarball instead.

packages/vms/build_curlbuild_h.com is obsolete with this change.

Accessing the library module name "tool_main" needs different handling
when the optional extended parsing is enabled.

Tested on IA64/VMS 8.4 and VAX/VMS 7.3
2013-03-20 20:44:57 +01:00
..
AIX
Android Tweak the Android.mk file for its new location 2013-02-06 23:44:49 +01:00
DOS packages/DOS/common.dj: remove COFF debug info generation 2013-01-10 19:58:59 +01:00
EPM
Linux
NetWare Removed trailing empty strings from awk script. 2012-07-12 00:07:01 +02:00
OS400 OS400: synchronize RPG binding 2013-03-12 15:37:34 +01:00
Solaris
Symbian Revert changes relative to lib/*.[ch] recent renaming 2013-01-06 18:20:27 +01:00
TPF
vms build_vms.com: use existing curlbuild.h and parsing fix 2013-03-20 20:44:57 +01:00
Win32
Makefile.am build: move Android.mk to packages/Android/ 2013-02-06 23:08:05 +01:00
README

                                  _   _ ____  _
                              ___| | | |  _ \| |
                             / __| | | | |_) | |
                            | (__| |_| |  _ <| |___
                             \___|\___/|_| \_\_____|

PACKAGES

 This directory and all its subdirectories are for special package
information, template, scripts and docs. The files herein should be of use for
those of you who want to package curl in a binary or source format using one
of those custom formats.

 The hierarchy for these directories is something like this:

   packages/[OS]/[FORMAT]/

 Currently, we have Win32 and Linux for [OS]. There might be different formats
for the same OS so for Linux we have RPM as format.

 We might need to add some differentiation for CPU as well, as there is
Linux-RPMs for several CPUs. However, it might not be necessary since the
packaging should be pretty much the same no matter what CPU that is used.

 For each unique OS-FORMAT pair, there's a directory to "fill"! I'd like to
see a single README with as much details as possible, and then I'd like some
template files for the package process.