Difference between revisions of "Programming Howto:Deploy a Release version of a BCI2000 Module"
|Line 37:||Line 37:|
... but when appending a ".zip" extension, you can see it's a ZIP
... but when appending a ".zip" extension, you can see it's a ZIP as well.
Revision as of 15:46, 16 August 2018
Globally enable application bundling
Double-click the "Configure.sh.cmd" script in the BCI2000 build directory to start the CMake GUI.
Make sure "USE_APPLICATION_BUNDLES" is checked, and click "Generate".
Switch to VisualStudio and click "Reload" if prompted.
Enable application bundling for your module
In your module's CMakeLists.txt, disable any "NOBUNDLE" option.
Rebuild your module
Switch to Release mode.
Right-click your module, and choose "Build" from the context menu.
When the bundle is created, a list of contained files will be shown.
The bundle looks like an executable ...
... but when appending a ".zip" extension, you can see it's a ZIP archive as well. At the beginning, there is an executable stub like in a self-extracting archive. Unlike a self-extracting archive, the bundle stub does not extract the archive's contents to disk but loads and runs them.
This allows you to move the module to a different machine without having to install additional software there.
NOTE: This does not work for debug builds, which will always depend on components installed alongside VisualStudio.