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

Buildozer feature redirect .buildozer folder outside your project #162

Closed
olymk2 opened this issue Nov 14, 2014 · 0 comments · Fixed by #163
Closed

Buildozer feature redirect .buildozer folder outside your project #162

olymk2 opened this issue Nov 14, 2014 · 0 comments · Fixed by #163

Comments

@olymk2
Copy link

olymk2 commented Nov 14, 2014

There does not seem to be a way to change this currently, causes issues if you use any kind of sync services and generally just fills your project with lots of files for the build process.

olymk2 pushed a commit to olymk2/buildozer that referenced this issue Nov 14, 2014
fixes kivy#161 checks if build-tools exists and returns if it does not so it can be fetched
fixes kivy#162 set builddir in you spec file so the packages are created outside your project
builddir = /tmp/buildozer/  # for example
olymk2 pushed a commit to olymk2/buildozer that referenced this issue Nov 14, 2014
fixes kivy#161 checks if build-tools exists and returns if it does not so it can be fetched
fixes kivy#162 set builddir in you spec file so the packages are created outside your project
builddir = /tmp/buildozer/  # for example
@tito tito closed this as completed in #163 Nov 22, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant