py-path.mk: Add file
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m9s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m22s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m4s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m34s
CI / Packaging test (push) Successful in 0s
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m9s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m22s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m4s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m34s
CI / Packaging test (push) Successful in 0s
Aside from PYTHONPATH, ldlibpath.mk runs jw-pkg.py for determining other paths, too, which is often unneeded and can impact performance. Split the PYTHONPATH detection into a dedicated py-path.mk, and include it from ldlibpath.mk, so it can be used instead where needed.
Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
parent
d57876a620
commit
d689d0b8bd
2 changed files with 7 additions and 6 deletions
|
|
@ -17,9 +17,4 @@ ifeq ($(origin JW_PKG_EXE_PATH),undefined)
|
|||
endif
|
||||
export PATH := $(JW_PKG_EXE_PATH)
|
||||
|
||||
# -- PYTHONPATH
|
||||
PYTHONPATH_ENV := $(PYTHONPATH)
|
||||
ifeq ($(origin JW_PKG_PYTHON_PATH),undefined)
|
||||
JW_PKG_PYTHON_PATH := $(call proj_query, pythonpath $(PROJECT))
|
||||
endif
|
||||
export PYTHONPATH := $(JW_PKG_PYTHON_PATH)
|
||||
include $(JWBDIR)/make/py-path.mk
|
||||
|
|
|
|||
6
make/py-path.mk
Normal file
6
make/py-path.mk
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
# -- PYTHONPATH
|
||||
PYTHONPATH_ENV := $(PYTHONPATH)
|
||||
ifeq ($(origin JW_PKG_PYTHON_PATH),undefined)
|
||||
JW_PKG_PYTHON_PATH := $(call proj_query, pythonpath $(PROJECT))
|
||||
endif
|
||||
export PYTHONPATH := $(JW_PKG_PYTHON_PATH)
|
||||
Loading…
Add table
Add a link
Reference in a new issue