StartMemPack: Difference between revisions
Jump to navigation
Jump to search
Francoisal (talk | contribs) No edit summary |
m (backlinks) |
||
| Line 15: | Line 15: | ||
| MEM_OPTIONS_WANTHEADERS || 1 || The output stream should include the complete headers (beginning+end) | | MEM_OPTIONS_WANTHEADERS || 1 || The output stream should include the complete headers (beginning+end) | ||
|} | |} | ||
{{backlink|Packer plugins developer guide|Packer plugins developer guide}} | |||
{{back|Packer plugins developer guide overview|Packer plugins developer guide overview}} | |||
{{back|GetPackerCaps|GetPackerCaps}} | |||
{{back|PackToMem|PackToMem}} | |||
{{back|DoneMemPack|DoneMemPack}} | |||
Latest revision as of 18:57, 18 April 2006
StartMemPack starts packing into memory. This function is only needed if you want to create archives in combination with TAR, e.g. TAR.BZ2. It allows Totalcmd to create a TAR.Plugin file in a single step.
int __stdcall StartMemPack (int Options, char *FileName);
Description
StartMemPack should return a user-defined handle (e.g. pointer to a structure) on success, zero otherwise.
- FileName refers to the name of the file being packed - some packers store the name in the local header.
- Options can contain a combination of the following values:
| Constant | Value | Description |
|---|---|---|
| MEM_OPTIONS_WANTHEADERS | 1 | The output stream should include the complete headers (beginning+end) |
Back to Packer plugins developer guide
Back to Packer plugins developer guide overview Back to GetPackerCaps Back to PackToMem Back to DoneMemPack