Add uic and rcc entry points

[n-elie]

Checklist

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

[conda-forge-webservices[bot]]

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) and found it was in an excellent condition.

[hmaarrfk]

I remember we manually had to move scripts around for pyside2.

https://github.com/conda-forge/pyside2-feedstock/blob/main/recipe/build.sh#L94

[hmaarrfk]

I also noticed that the script did little other than to call

uic -g python

Most of the script tried to work around issues of finding the binary when shipped within python's virtual environments.

[hmaarrfk]

and our patch: https://github.com/conda-forge/pyside2-feedstock/blob/main/recipe/patches/pyside2-tools-obsolete.patch

[n-elie]

@hmaarrfk Thanks for the hints. I managed to get something working on linux and osx, but the build is failing for some reasons in windows and aarch64. These failures does not seem to be related to my modifications.

[hmaarrfk]

Does or "does not"?

[n-elie]

"does not", sorry

[hmaarrfk]

I typically verify by creating a mostly empty pull request and rerendering there. lets do that?

[jschueller]

Could you try rebase ? the clang pinning and patch should not be necessary anymore

[n-elie]

@jschueller I was trying to rebase but it seems you are working on it in #182

[jschueller]

yes, I included your work

[n-elie]

Great, thank you