Select this option to scan your scripts for dependencies without procedding to a build. Once a scan has completed successfully you will then be able to build your application. When you run a scan, all the calculated and explicit dependencies are stored ready for a build. If you make changes to explicit dependencies, for example to add additional modules or executables, you must run a scan again. Following a successfull scan, information is available under the Scan Tree Node
Perform Build Only
If a successfull scan has been completed you will be able to build your project. When you run a build, dependencies are taken from the results of the last scan. If you make changes to explicit dependencies, for example to add additional modules or executables, you must run a scan again. You CAN make amendments to your build after a scan using the options available under the Build Tree Node. Generally you should use the Scan & Build Option to build your projects. Performing a build without automatically scanning first is the most common cause of errors in the built executable package.
Show Shared Libraries
Toolbar -> Show Shared Libraries
If a successfull scan has been completed you will be able to inspect your project for an indication of the shared libraries that you may have to package. This option produces a list of the shared libraries loaded by the modules in your project. See Shared Library Dependencies for more detailed information.
Scan & Build Scripts
Toolbar -> Scan & Build Scripts
This combines the operations of Scan and Build on your project. It is the standard way to produce your executable package. You should always use this option (rather that 'Perform Build Only') unless you are absolutley certain that nothing has changed either in your source code or within Cava Packager since your last scan.
Change Project Name
Use this option to change your Project Name
Make a copy of the current project in a new folder. You can use this option to create a new project based on the current one or perhaps to backup the essential settings of your project without including the current scan, diagnostic and release files.
If you are creating a new project, be sure to change the project name and to assign a new product class id.
Copy the current project to a single portable file. You can then use this file to create a new project on this machine, or on another machine. The exported project file is portable across operating systems.