Replies: 1 comment
-
No. The recipe folder should only contain the recipe configuration, any patch files needed to compile the package, and the test files (although the test files aren't currently used). If litesync requires some external headers to build, that implies there's a non-Python dependency. Those dependencies need to be packaged as a separate recipe (see, for example libjpeg and Pillow). If litesync provides headers, they should be in the source tarball; if they're needed for other packages that depend on litesync, they should be in the wheel that is produced - but they should already be packaged like that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would like to ask a question. Are the iOS static libraries and header files related to litesync placed in the lib and include folders of
recipes/litesync/opt/
?Beta Was this translation helpful? Give feedback.
All reactions