![]() 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 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |