You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-16
Original file line number
Diff line number
Diff line change
@@ -15,23 +15,8 @@ Current flow to update dependencies:
15
15
-https://docs.conan.io/2/reference/conan_server.html (not recommended by Conan)
16
16
-https://jfrog.com/
17
17
18
-
- Switch to conan 2. Incomplete (and potentially outdated) PR can be found here: https://github.com/vcmi/vcmi/pull/1603 Will also require changing how we create final package - instead of archiving `~/.conan/data` we'll need to use `conan cache` command
19
-
20
-
- Use Conan for msvc builds. Currently blocked by several issues, namely:
21
-
- Conan 1 does not works with latest Visual Studio 2022. We need to either use msvc 2019 or upgrade to conan 2.
22
-
- ffmpeg fails to find its dependencies when building with conan 1 + msvc 2019. Might be fixed in conan 2.
23
-
- Qt fails to build due to broken string escaping in a path (conan 1 + msvc 2019)
24
-
25
-
- Rebuild SDL_mixer and try to enable support for opus and flac. Needs investigation as to why libopus / libflac fail to build
26
-
27
-
- Consider removing pcx support from SDL_image
28
-
29
18
- Rebuild ffmpeg with libdav1d and av1 support enabled. Needs investigation as to why dav1d fails to build on mingw and on android.
30
19
31
-
- Find out why libiconv fails to rebuild on Android
32
-
33
-
- Rebuild entire package from scratch using latest recipes from conan, to test current version of recipes
34
-
35
20
- Run CI with full package rebuild on schedule (weekly? monthly?) to detect any regressions or breaking changes in CI or in used recipes
36
21
37
22
- Automatically generate Github release with updated packages as part of CI. Should probably be done only for changes in main branch and/or for manually triggered workflows
@@ -49,4 +34,4 @@ With this approach we will be able to use following flow for new dependencies:
49
34
50
35
After merging PR in vcmi/vcmi repository vcmi will use new dependencies.
51
36
52
-
If vcmi/vcmi PR is discarded for one reason or another, changes in this repository will have to be discarded as well
37
+
If vcmi/vcmi PR is discarded for one reason or another, changes in this repository will have to be discarded as well
0 commit comments