Pre-release 0.5

     __                    __           _       _
  /\ \ \_____   _____ _ __/ _\ ___ _ __(_)_ __ | |_
 /  \/ / _ \ \ / / _ \ '__\ \ / __| '__| | '_ \| __|
/ /\  /  __/\ V /  __/ |  _\ \ (__| |  | | |_) | |_
\_\ \/ \___| \_/ \___|_|  \__/\___|_|  |_| .__/ \__|
                                         |_|
           The QB programming language.
----------------------------------------------------

Release 0.5

Usage of ns:
  -c string
        Specify a file to compile (.ns).
  -decompileWithRoq
        Display output from roq decompiler (roq.exe must be in your PATH).
  -o string
        Specify the output file name.
  -p string
        Specify a pre spec file (.ps).
  -showHexDump
        Display the output in hex format (e.g. compiled bytecode or raw pre file).

Generating a PRE/PRX file:

You can generate a pre/prx file by providing a pre spec.

$ ns -p myPreSpec.ps -o bundle.pre

This will read the pre spec from myPreSpec.ps and create a new PRE file: bundle.pre

• Use -showHexDump to see the bytes of the pre file.

What's a pre spec?

This is a text document containing many "items".

Each "item" consists of:

1. The source path (the file to bundle).
2. The destination path (inside the pre file).

Here's an example of a pre spec containing 4 items:

C:\mod\build\qb\_mods\byxor_debug.qb
qb\_mods\byxor_debug.qb

C:\mod\build\qb\_mods\byxor_menu.qb
qb\_mods\byxor_menu.qb

C:\mod\build\qb\_mods\byxor_math.qb
qb\_mods\byxor_math.qb

C:\mod\qdir.txt
code\qb\qdir.txt

Note

• Only pre version 3 is supported at the moment.
• None of the items inside the pre file will be compressed.
• You can use relative paths too.