conan-config

Commit Graph

Author	SHA1	Message	Date
j.spijker@ultimaker.com	89300371e1	Use the correct venv_folder when not in local cache Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	c10fb89ca2	Fix source install If the package not in local cache then the user_info isn't defined yet Contributes to CURA-9365	4 years ago
Ghostkeeper	b3574a58aa	Loosen up path check for pip_requirements On Linux and MacOS it's provided with the full path here. This is a simple (albeit overly loose) way to allow that. Contributes to issue CURA-9365.	4 years ago
Ghostkeeper	5cd446306f	Add pip_requirements_build to venv generator Then it will also install the build-requirements into that virtual environment, such as Pyinstaller. Contributes to issue CURA-9365.	4 years ago
j.spijker@ultimaker.com	d2e410f897	Add shared libs in site-packages to env PATHs Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	879d5fcdda	Use regular conan script generation Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	533035ec5f	Fixed creating VirtualPythonEnv from remote install Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	c06ee39be6	run python with the run environment This should allow for using the cpython dependency Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	91b9d5f5d0	Use the pathlib module Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	f74e045b69	Use the CPython dependency for the VirtualPythonEnv Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	639b8ef9dc	Remove win_bash arg No longer needed, was a remnant of the old path troubles Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	0fc21e82b3	Install wheels and setuptools as base Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	cd24959ffc	Use the correct Env naming scheme depending on OS Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	34c3fb69d1	Use the correct quotes for each OS Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	332fa8f5e4	Uniform name for python executable on all three OSes Make sure there executable is named the same on all three OSes this allows it to be called with `python` simplifying GH Actions steps. So I don't have to add exceptions based on the OS in the runner Matrix Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	8a9b5a0e86	Renamed activate_github_actions_env Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	e8ba061446	Construct the GH Action environments for the PythonVirtualEnv Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	85c4936234	Generate the activation scripts Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	d2d8c2cca7	Switched quote characters https://cpplang.slack.com/archives/C41CWV9HA/p1654942697502539 Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	ff842cba50	Make the VirtulPythonEnv more robust It should now be able to also create a venv with another interpreter. Provided it is installed next to the current interpreter on the same base Path. Trying to make execution of the run commands robust on Windows, till no avail. It states: ```powershell ----Running------ > C:\'Program Files'\Python310\python.exe -m venv venv ----------------- 'C:\'Program' is not recognized as an internal or external command, operable program or batch file. ``` But if I run the ` C:\'Program Files'\Python310\python.exe -m venv venv` in the same shell manually it executes correctly. Contributes to CURA-9365	4 years ago
j.spijker@ultimaker.com	bdfccc2f0e	VirtualPythonEnv generator added This generator can be used from the commandline as: `conan install . -g VirtualPythonEnv` It will then create a virtual environment in the build folder based on the sys interpreter of a specified interpreter in the conanfile The venv can be activated as normal Contributes to CURA-9177_Fix_CI_CD	4 years ago

21 Commits (89300371e16650ade3686147686df5636762b1f9)