You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a electron native module that integrates with a third party library. The third party library has different configurations (x86 v.s. x64, Debug v.s. Release). I am thinking if it is a good idea to have electron-builder's extraFiles and extraResources accept file path with environmental variables. For example,
I have a electron native module that integrates with a third party library. The third party library has different configurations (x86 v.s. x64, Debug v.s. Release). I am thinking if it is a good idea to have electron-builder's
extraFiles
andextraResources
accept file path with environmental variables. For example,If I set env
PLATFORM
tox86
andDEBUG_RELEASE
toRelease
. I want the files inthird_party/x86/Debug
to be copied to./
.Right now I can workaround this by having another script that modifies
package.json
based on different configurations.The text was updated successfully, but these errors were encountered: