My electron app for Mac OSX has sox dependency. What's the best way to include it as part of electron-package? I'd prefer the user not having to install sox separately (unfortunately most of my users are not that savy). Is there a way to include sox binaries directly or sequence pre-install of sox before my app?
I ended up including the sox binary into the package. I used node-record-lpcm16 package and updated its path to use included sox binary. This way I can pass down the the lib path as a parameter.
Related
I made an Electron app, but it is unnecessarily trying to install itself on some platforms. My app is very simple enough that it makes more sense to be a non-installing executable. Is there an option for this?
You can set target to portable . This will directly run your executable without any installer.
You can find more information here: https://www.electron.build/configuration/nsis#portable
I am currently building a console package with Dart, and Rust using FFI(foreign function interface). Since I can't/shouldn't publish dll/so/dylib files, how can I add a build functionality to it. With that functionality, the required files should be built after the package is downloaded, so that the interop-ed code can work properly. How can it be done? Will the user that downloaded the package need to have Rust in his machine to build the files?
You need to either distribute binaries or require the user to have a Rust compiler.
Im using Wxlua for a GUI im building but need minizip for one of my functions but have no idea how to install minizine to my lua dir.
I expect minizip = require('minizip') to work with my wxlua
minizip is not part of wxlua, so you need to follow the instructions from the source you got the package from. For example, this package provides all the necessary binaries, but requires LuaJIT or lua+luaffi to run.
Usually, it's sufficient to place binary files (*.so or *.dll) into a folder listed in package.cpath and lua files into a folder listed in package.path, but those files may have their own dependencies, so it's better to consult documentation for the module.
Is there a standard or recommended installation directory for the Dart language? If so, I would like to know what it is for both Windows and Mac. I searched online on dartlang.org, Google, and StackOverflow. For Mac specifically, I have seen many programming languages installed under /Library.
I believe the standard workspace for Dart projects is ~/dart. When you download the Dart language, you are given a /dart folder containing the Editor, SDK, Chromium with Dart VM installed, and some extras. I am wondering what the standard location for this folder is. Thank you in advance!
The standard workspace directory for Dart projects is like you wrote ~/dart in Linux (don't know about other OS).
The standard installation directory is depending on conventions of your OS than the Dart language.
You should have an environment variable DART_SDK pointing to the dart-sdk subdirectory of the installation directory and include the DART_SDK/bin in your path.
On MAC, just drop the directory on App directory, then in terminal you put : "export PATH=$PATH:/Applications/dart/dart-sdk/bin"
I am building an app that I eventually would like to release on Cydia, however I'm having trouble finding any good documentation on developing apps for jailbroken devices. So firstly, if you have any good links for developing for jailbroken iOS devices that would also be much appreciated!
My current problem is that for my app to work I would require tools from other packages on Cydia like otool and possibly some script interpreter (haven't decided which one yet). Is there a way that I can have these dependencies install alongside my current app in Cydia? I feel like I've seen it before downloading other apps.
Yes, absolutely.
When you build your app, you should make sure to bundle it as a Debian package. Some repositories will let you just give them a normal .app bundle, which they will then use to build a .deb file. But, if you want this, I'd recommend learning to build a .deb bundle yourself. More instructions from Saurik here.
Inside the .deb bundle, you will have a DEBIAN subdirectory, with a file inside named control:
DEBIAN/control
DEBIAN/postinst
DEBIAN/postrm
DEBIAN/preinst
The control file is where the Cydia store app description, the app version number (used by the store), and a bunch of other information goes. An optional field in the control file lets you specify that your app has dependencies. If you list another package as a dependency, that package will automatically get installed when Cydia installs your app. Something like this:
Depends: bigbosshackertools
This line is to specify a dependency on the BigBoss Recommended Tools package (which is a very large set of packages, so be aware that you're adding a large install set to your own app).
Or, you could try
Depends: odcctools
to use Saurik's Darwin CC Tools package.
I have been building jailbreak apps for a while, so I do it with homemade scripts, but there's now a tool for helping with this called iOSOpenDev. You could use that to build your package, and edit your control file, if you aren't already familiar with .deb packages, and don't want to bother (although I'd recommend learning).