Generate-evb takes care of generating the project file. You can use this module along with generate-evb, where enigmavirtualbox takes care of installing, packing and Generate a project file (currently this is very limited and not customizable).AlternativesĮnigmavirtualbox is a Node.js module and CLI, that offers the We will use theĭefault templates for any missing template, so you don't have to replace all of them. To make generateEvb use the updated templates just pass it the optional options.templatePath object. Then you can go back to the templates copy, and modify Then you should do a diff between the beforeĪnd after, so you will see what options need changing. Use enigmavb.exe (Enigma's GUI) to change the options as you see fit. If you can't find the option, I suggest that you generate the project file using the default options and The templates are xml files that are pretty descriptive, so for most options it should be easy to figure our what needsĬhanging. The default template files are located at generate-evb/templates.īefore you change them, copy the templates to a location outside of node_modules. you want to add virtual registry entries), you can use custom templates. If an option/setting you are looking for is notĪvailable there (e.g. You can customize the generated project using options.evbOptions. execFile ( evbCliPath, , function ( err, stdout, stderr ) ) Customization Var fs = require ( 'fs' ) var child_process = require ( 'child_process' ) // Change the following paths to the actual paths used in your project var evbCliPath = 'C:/Program Files (x86)/Enigma Virtual Box/enigmavbconsole.exe' var projectName = 'build/packedNode.evb' var inputExe = 'C:/Program Files (x86)/nodejs/node.exe' var outputExe = 'build/node.exe' child_process. And we will save the evb project to build/packedNode.evb, so that's We want to save the packaged executable toīuild/node.exe so that will be our outputExe. (all paths can be relative or absolute), so that's our path2Pack. Our copy of node.exe is located atĬ:/Program Files (x86)/nodejs/node.exe, so that will be our inputExe. Let's say that we want to pack a Node.js project into node.exe. allowRunningOfVirtualExeFiles (Boolean) - same as Enigma's "Options Tab > Allow running of virtual.mapExecutableWithTemporaryFile (Boolean) - same as Enigma's "Options Tab > Map executable files using.shareVirtualSystem (Boolean) - same as Enigma's "Options Tab > Share virtual system to child processes".compressFiles (Boolean) - same as Enigma's "File Options > Compress Files".deleteExtractedOnExit (Boolean) - same as Enigma's "File Options > Delete Extracted On Exit".file (String) - path to a file template.dir (String) - path to a directory template.project (String) - path to a project template.templatePath (Object) - optional, will default to the templates in the generate-evb/templates.Or directory you want to pack, and false for anything else The function should return true for any file (String), isDir (Boolean) for each directory and file in path2Pack. filter (Function) - optional, this function is called with the following parameters: fullPath (String), name.path2Pack (String) - the path to the directory with the content that we want to pack into the copy of inputExe.Enigma saves the packed file to this path outputExe (String) - the output executable file path.Enigma packs the files from path2Pack into a copy of this inputExe (String) - the input executable file path. projectName (String) - the file path to which we want to save the generated evb file (e.g.GenerateEvb ( projectName, inputExe, outputExe, path2Pack, options ) Start by installing generate-evb locally: You can also wrap your code in a gulp/ grunt task if you Update the project file, you just re-run your build script. You can use generate-evb in your node build script, to pack an entire directory structure. You have to update the project manually using the GUI. In other words, if files were changed in one of the packed folders, Support for recursively packing an entire directory. The tool offers only a GUI for creating the project and there's no built-in To create a packaged executable you need to create a project file that describes what needs to be packaged along with images/logo.png, you can read the file from that path). Packaged executable can read/execute files that were packed with it as if they were really in the file system and not The tool takes care of all the virtualization, so you usually don't need to change your code in any way. To help you automate the process of generating an 'Enigma Virtual Box' project file (*.evb) as part of your normal buildĮnigma Virtual Box (EVB) is a tool that lets you package a WindowsĮxecutable with all of the data and dependencies it needs in-order to run (dll files, assets, registry entriesĮtc.).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |