Even though we had to patch these recipes, the user/channel
shouldn't be necesary any more because of the order in which
our remotes are defined in the conan-config repo. It will
first look into our own remotes, before going over to
conan-center-index.
Once the packages upstream are fixed for us, then we can use
the conan-center-index packages again, without changing the
code.
Contributes to CURA-9365
Once upstream recipes are fixed these can be removed again.
export the changes for now
```
# Export patched conan-center-index recipes, I will open PR's for all of those
git clone https://github.com/jellespijker/conan-center-index.git
pushd .
cd conan-center-index
git checkout fix_tcl_recipe_env_info
conan export recipes/tcl/all tcl/8.6.10@ultimaker/testing
git checkout fix_tk_recipe_env_info
conan export recipes/tk/all tk/8.6.10@ultimaker/testing
git checkout fix_mpdecimale_recipe_not_use_msys
conan export recipes/mpdecimal/2.5.x mpdecimal/2.5.1@ultimaker/testing
git checkout add_3_10_4_version_cpython
conan export recipes/cpython/all cpython/3.10.4@ultimaker/testing
```
Contributes to CURA-9365
This should make things more agnostic.
although technically not needed for Uranium
and already implicitly defined as a requirement
of pyArcus. I think it is good to include this
requirement here as well. For Unit Testing etc.
Contributes to CURA-9365
Repo's such as fdm_materials and cura-binary-data don't
need to build we can just export pre-build binaries
and files with the recipe
Contributes to CURA-9365
Added a recipe in the conan-ultimaker-index repo,
which contains a conanrecipe that can be loaded
as a python_requires.
This allows us to reuse python code over multiple
recipes, see: https://docs.conan.io/en/latest/extending/python_requires.html
Contributes to CURA-9365
With the new PyCharmRunEnv generate conan
should automatically create a pycahrm run
target, setting the paths correctly.
Usage as: `conan instal ....... -g PyCharmRunEnv`
Contributes to CURA-9365
https://docs.conan.io/en/latest/versioning/version_ranges.html
It won't match build metadata otherwise.
The order of search for matching versions is as follows:
First, the local conan storage is searched for matching versions, unless the --update flag is provided to conan install.
If a matching version is found, it is used in the dependency graph as a solution.
If no matching version is locally found, it starts to search in the remotes, in order. If some remote is specified with -r=remote, then only that remote will be used.
If the --update parameter is used, then the existing packages in the local conan cache will not be used, and the same search of the previous steps is carried out in the remotes. If new matching versions are found, they will be retrieved, so subsequent calls to install will find them locally and use them.
Contributes to CURA-9365
No longer download and mess with sources from
other repo's.
Created Conan packages for cura-binary-data,
fdm_materials and uranium.
Charon is installed with pip. I had to create
a separate requirement file for that since
you can't mix and match git and hashes.
Contributes to CURA-9365
I tried updating when the qualities change but this was updating before this line
if(recommendedResolutionSelector._previousResolution !== Cura.MachineManager.activeQualityType)
which caused this always to resolve as true
The solution was to update _previousResolution after we select an item in the drop down.
CURA-8849
Our Free tier server has reached it's limit.
This should ensure that we don't use or
ultimaker server. Once the new infrastructure
is in place we should revert this
Contributes to CURA-9365
