feisty meow concerns codebase  2.140
/opt/feistymeow.org/feisty_meow/nucleus/applications/bundler/manifest_format.txt File Reference

Variables

the unpacking manifest is a structure defined in terms of bytes the exe s manifest offset is set to point to the beginning of this structure bytes content
 

Variable Documentation

◆ content

the unpacking manifest is a structure defined in terms of bytes the exe s manifest offset is set to point to the beginning of this structure bytes content
Initial value:
=> 3 number of chunks in the TOC
4 => 4+N-1 first manifest item, with length N
4+N => 4+N+M-1 second item, with length M
4+N+M =>...etc.
each bundle chunk has a structure:
bytes content
----- -------
0 => 3 size of the data component of the chunk
4 => 4+S-1 the file system target location for this chunk, as a zero
terminated string (of length S). this string comes from the
target defined in the packing manifest.
then the data starts after the end of the TOC

Definition at line 7 of file manifest_format.txt.

Referenced by textual::xml_generator::add_content(), add_include(), textual::xml_parser::content_callback(), creatapose(), configuration::registry_configurator::get_section(), getfile(), org.feistymeow.windowing.WindowUtilities::openInJFrame(), and structures::string_table::unpack().

file
a second double hyphen terminates this special treatment In this m ma ak ke ed de ep pe en nd d can be made to safely ignore esoteric com piler arguments that might normally be found in a CFLAGS m ma ak ke e macro(see the EEXXAAMMPPLLEE section above). All options that mmaakkeeddeeppeenndd recognizes and appear between the pair of double hyphens are processed normally. AALLGGOORRIITTHHMM The approach used in this program enables it to run an order of magnitude faster than any other "dependency generator" I have ever seen. Central to this performance are two assump- tions and that most files in a single directory will include largely the same files Given these m ma ak ke ed de ep pe en nd d expects to be called once for each with all source files that are main tained by the makefile appearing on the command line It parses each source and include file exactly maintain ing an internal symbol table for each the first file on the command line will take an amount of time proportional to the amount of time that a normal C preprocessor takes But on subsequent if it encounter s an include file that it has already it does not parse it again For imagine you are compiling two _ f_ i_ l_ e_ _ c and _ f_ i_ l_ e_ _ they each include the header file _ h_ e_ a_ d_ e_ r_ _ and X Version Last _ h_ e_ a_ d_ e_ r_ _ h and then _ d_ e_ f_ _ h and _ d_ e_ f_ _ h_ It then decides that the dependen cies for this file are file1 includes _ h_ e_ a_ d_ e_ r_ _ it does not parse the file
Definition: makedepend.txt:218
the
for all bundled products if it is going to be it should be the
Definition: example_manifest.txt:38
content
the unpacking manifest is a structure defined in terms of bytes the exe s manifest offset is set to point to the beginning of this structure bytes content
Definition: manifest_format.txt:7