Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow usage of environmental variables in extraFiles and extraResources #1307

Closed
liusy182 opened this issue Feb 27, 2017 · 2 comments · May be fixed by qcif/data-curator#563
Closed

Allow usage of environmental variables in extraFiles and extraResources #1307

liusy182 opened this issue Feb 27, 2017 · 2 comments · May be fixed by qcif/data-curator#563
Labels

Comments

@liusy182
Copy link

  • Version: 14.1.1
  • Target: Windows

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,

 "extraFiles": [{
      "from": "third_party/%PLATFORM%/%DEBUG_RELEASE%",
      "to": "./"
    }],

If I set env PLATFORM to x86 and DEBUG_RELEASE to Release. I want the files in third_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.

develar added a commit to develar/electron-builder that referenced this issue Feb 27, 2017
develar added a commit that referenced this issue Feb 27, 2017
@develar
Copy link
Member

develar commented Feb 27, 2017

${env.ENV_NAME} — any environment variable.

@liusy182
Copy link
Author

That is fast. Thanks a lot !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants