Skip to content

Do not symlink build-tools directory #1694

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

Merged
merged 1 commit into from
Apr 19, 2016

Conversation

rosen-vladimirov
Copy link
Contributor

Due to latest changes in Android runtime, we can no longer symlink build-tools directory from the runtime when --symlink is passed.
There are two major reasons:

  • There are .js files in the build-tools, which use require(<smth>). This is failing as node's searching for the installed modules from the original location of the file.
  • During build, new files are generated in the build-tools directory. As they are unique (each one is project specific), we cannot symlink them.

Due to latest changes in Android runtime, we can no longer symlink `build-tools` directory from the runtime when `--symlink` is passed.
There are two major reasons:
- There are `.js` files in the build-tools, which use `require(<smth>)`. This is failing as node's searching for the installed modules from the original location of the file.
- During build, new files are generated in the build-tools directory. As they are unique (each one is project specific), we cannot symlink them.
@rosen-vladimirov rosen-vladimirov self-assigned this Apr 19, 2016
@rosen-vladimirov rosen-vladimirov added this to the 2.0 milestone Apr 19, 2016
@Mitko-Kerezov
Copy link
Contributor

👍

1 similar comment
@vchimev
Copy link

vchimev commented Apr 19, 2016

👍

@rosen-vladimirov rosen-vladimirov merged commit 777e18e into release Apr 19, 2016
@rosen-vladimirov rosen-vladimirov deleted the vladimirov/fix-android-symlink branch April 19, 2016 15:19
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 this pull request may close these issues.

3 participants