Thanks for the report. Those symbols come from sharpyuv/sharpyuv.c and sharpyuv/sharpyuv_csp.c. Can you make sure that those are included in the build output from bazel and give the compile command line used? You can also check the contents of libwebp.a with `nm`.
victo… via monorail
unread,
Jul 10, 2024, 4:18:27 AM7/10/24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
> Can you make sure that those are included in the build output from bazel
The package build file is shown in the Gist I attached. It uses "configure_make", which would seem to actually build it as described in the repository's README.
> give the compile command line used
This I am not sure how to extract from Bazel. Could you please advise?
victo… via monorail
unread,
Jul 10, 2024, 4:23:29 AM7/10/24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
The nm output shows the library does not contain the symbols. Reading your initial post I thought the build was pulling sources from the glob, which looks like it would pick up all the files in the tree (**/*.[ch] or src/**/*.[ch] and sharpyuv/*.[ch] are probably enough). If `configure_make` is actually executing configure and running make, then you'll need to add libsharpyuv.a to your link. The sharpyuv files are built into a separate library with configure to allow the functions to be reused elsewhere.
> Update: By digging a bit with "bazel aquery", I was able to find what looks like the script for building libwebp within my workspaace.
Thanks I don't see anything out of the ordinary for the build flags. Another quick way to see the command line for a particular file is to use `--verbose_failures` and add a `#error` to the source file.
victo… via monorail
unread,
Jul 11, 2024, 5:43:51 AM7/11/24
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
> Your pointers were actually super helpful! I managed to get it working by building it as:
Thanks for the update. I'm glad you got it to work.
> Is there a way we can include some information on building this library through Bazel in the README of the repository?
Right now there isn't too much to add given we don't maintain a bazel build file for the project. If we did we might go with a direct source/module list rather than configure_make. In your example there are some options being disabled which we might like to retain.
If you have ideas for the documentation or a bazel file please feel free to send a patch: