|
|
|
|
####-*.patch
|
|
|
|
|
*.pyc
|
|
|
|
|
*.swp
|
|
|
|
|
build/
|
|
|
|
|
dist/
|
|
|
|
|
*.egg/
|
|
|
|
|
Electrum.egg-info/
|
|
|
|
|
electrum/locale/
|
|
|
|
|
.devlocaltmp/
|
|
|
|
|
*_trial_temp
|
|
|
|
|
packages
|
|
|
|
|
env/
|
|
|
|
|
.buildozer/
|
|
|
|
|
bin/
|
|
|
|
|
/app.fil
|
|
|
|
|
.idea
|
|
|
|
|
.mypy_cache
|
|
|
|
|
.vscode
|
windows: when running from source, with py3.8+, load DLLs from '.dlls'
Python 3.8 changed where DLLs are searched for.
see https://docs.python.org/3/whatsnew/3.8.html#bpo-36085-whatsnew
This potentially affect our binaries when we start shipping python 3.8+, however that is not being addressed here. This commit simply addresses the usecase of running from source, on Windows, using python 3.8.
On older Python, a user could build/obtain DLLs and place them anywhere on the system %PATH%, however this no longer works with py3.8, as %PATH% is no longer checked.
With py3.8, instead, we now check if there is a folder named '.dlls' in the top-level project directory, and if so, register that as an additional search path.
A user who wants to run Electrum from source on Windows using python 3.8 or later, with their custom DLLs, should manually create the '.dlls' folder and put their DLLs there. If they also want to switch between e.g. python 3.7 and 3.8, they should also include '.dlls' in the system %PATH%.
When using Electrum, interesting DLLs include at least libsecp256k1.dll, libusb-1.0.dll, libzbar-0.dll.
5 years ago
|
|
|
.dlls
|
|
|
|
|
|
|
|
|
|
# icons
|
|
|
|
|
electrum/gui/kivy/theming/light-0.png
|
|
|
|
|
electrum/gui/kivy/theming/light-1.png
|
|
|
|
|
electrum/gui/kivy/theming/light.atlas
|
|
|
|
|
|
|
|
|
|
# tests/tox
|
|
|
|
|
.tox/
|
|
|
|
|
.cache/
|
|
|
|
|
.coverage
|
|
|
|
|
.pytest_cache
|
|
|
|
|
|
|
|
|
|
# build workspaces
|
|
|
|
|
contrib/build-wine/tmp/
|
|
|
|
|
contrib/build-wine/fresh_clone/
|
|
|
|
|
contrib/build-linux/appimage/build/
|
|
|
|
|
contrib/build-linux/appimage/.cache/
|
|
|
|
|
contrib/android_debug.keystore
|
