Build Windows library as shared

[jeongseok-meta]

This is a temporary solution until it's addressed in the upstream, such as flexible-collision-library/fcl#461. Until then, I've added a minimal patch to enable building as shared libraries on Windows. It has been tested by building and running the unit tests.

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Closes #18

[jeongseok-meta]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jeongseok-meta]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12601606464. Examine the logs at this URL for more detail.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12605776726. Examine the logs at this URL for more detail.}

[jeongseok-meta]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[jeongseok-meta]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12606823231. Examine the logs at this URL for more detail.}

[jeongseok-meta]

@traversaro Could you please take a look when you have a chance? Thanks!

[traversaro]

@traversaro Could you please take a look when you have a chance? Thanks!

Thanks for working on this! Doing the switch static --> shared without a package version number is a bit brittle, as downstream package will have a run_exports of fcl 0.7.0 could be either a static library or a shared library. Anyhow, the shared library will have an higher build number, so hopefully we will be good to go.

Until then, I've added a minimal patch to enable building as shared libraries on Windows.

It does not seem that the repo upstream is particularly active, so if nothing that changes the probability of upstream getting support for building shared libraries on Windows is quite low, right?

[traversaro]

@jeongseok-meta feel free to also add you as maintainer here if you like.

[jeongseok-meta]

Doing the switch static --> shared without a package version number is a bit brittle, as downstream package will have a run_exports of fcl 0.7.0 could be either a static library or a shared library.

That's a good point. I hope this doesn't cause significant downstream issues.

It does not seem that the repo upstream is particularly active, so if nothing that changes the probability of upstream getting support for building shared libraries on Windows is quite low, right?

Unfortunately, I think so. I plan to continue maintaining the upstream FCL by resolving build issues, including shared build fixes, without adding new features. However, I don't have a specific timeline for this at the moment..

[jeongseok-meta]

@jeongseok-meta feel free to also add you as maintainer here if you like.

I'm already a maintainer, thanks to you! :D

[traversaro]

@jeongseok-meta feel free to also add you as maintainer here if you like.

I'm already a maintainer, thanks to you! :D

Ah great. :D