miniscript: add version 1.6.2

[toge]

Specify library name and version: miniscript/1.6.2

• follow library names in 1.5.1
• use upstream CMakeLists.tt in 1.6.2
• follow API changes since 1.6.2

---

• I've read the contributing guidelines.
• I've used a recent Conan client version close to the currently deployed.
• I've tried at least one configuration locally with the conan-center hook activated.

[AbrilRBS]

Dum dum CI did not post the results, sorry about that. Restarting v1, but v2 failed https://c3i.jfrog.io/c3i/misc-v2/summary.html?json=https://c3i.jfrog.io/c3i/misc-v2/logs/pr/22861/6-windows-msvc/miniscript/1.5.1//summary.json for a proper reason

[uilianries]

Hello @toge The version 1.6.2 has a CMakeLists.txt supported: https://github.com/JoeStrout/miniscript/blob/v1.6.2/CMakeLists.txt

Is is not enough to build the project?

[toge]

@uilianries
Hello uilianries.
Thanks you for your review.

I know that.
If version is 1.6.2, this recipe tries to use CMakeLists.txt from upstream.

[conan-center-bot]

Conan v1 pipeline ✔️

All green in build 4 (1a58545490a5946685cf09f9bc09afa95800f21b):

• miniscript/1.5.1:
  All packages built successfully! (All logs)

• miniscript/1.6.2:
  All packages built successfully! (All logs)

---

Conan v2 pipeline ✔️

Note: Conan v2 builds are now mandatory. Please read our discussion about it.

All green in build 4 (1a58545490a5946685cf09f9bc09afa95800f21b):

• miniscript/1.5.1:
  All packages built successfully! (All logs)

• miniscript/1.6.2:
  All packages built successfully! (All logs)

[uilianries]

Suggested change

	if Version(self.version) >= "1.6.2":
	tc.variables["CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS"] = True
	else:
	tc.variables["MINISCRIPT_SRC_DIR"] = self.source_folder.replace("\\", "/")
	if Version(self.version) < "1.6.2":
	tc.variables["MINISCRIPT_SRC_DIR"] = self.source_folder.replace("\\", "/")

I would not enforce shared libraries in Windows. Instead, I would recommend asking support from the upstream directly. Remember that CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS really fragile, it not only exposes all symbols, including those that should be private, but also lacks exposing public static variables, which causes runtime errors when being consumed (e.g. libcoro).