Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

[SDWebImage] How can I use this alongside FFImageLoading without breaking the linker with duplicate symbols? #673

Open
KRA2008 opened this issue Sep 24, 2019 · 8 comments
Assignees

Comments

@KRA2008
Copy link

KRA2008 commented Sep 24, 2019

[SDWebImage]

I have an existing Xamarin.iOS application that uses SDWebImage that I want to start adding Native Forms to, and for the Native Forms pages I want to use FFImageLoading. However, when I add them both to the project (and then also use a bit of their code in AppDelegate.cs) I get tons of errors like:

Native linking failed, duplicate symbol: '_WebPAllocateDecBuffer'.

Duplicate symbol in: /.../liblibwebp.a(buffer_dec.o) (Location related to previous error)

Duplicate symbol in: /.../WebP.a(libwebpdspdecode_neon_la-alpha_processing_neon.o) (Location related to previous error)

Is this because they both have their own bindings to WebP? How can I work around that?

tuyen-vuduc pushed a commit to NAXAM/WebP.Touch that referenced this issue Oct 9, 2019
…arinComponents repository

- Use libwebp from SDWebImage
- Update libwebp version to v1.0.3
- Use carthage for compiling libwebp depedency
- Use libwebp framework instead of A file
- Copy dependent frameworks to frameworks for future references
- Update Nuget package to v1.0.7.3
@adrianknight89
Copy link

I have this issue as well when I want to create a custom Forms renderer that uses SDWebImage while FFImageLoading is already being used in Forms. Until this issue is fixed, I can't make further progress.

@Redth Is there a temporary workaround?

@Redth
Copy link
Member

Redth commented Oct 25, 2019

@SotoiGhost can you comment on this?

@PawKanarek
Copy link

PawKanarek commented Dec 3, 2019

Do you have any ideas how to deal with it? I also want to use SDWebImage alongside with FFImageLoading.

@PawKanarek
Copy link

Resolved this by deleting FFimage in favor of SDWebImage & Glide. I decided on that move because i wanted to share 1 library for all of my iOS projects. (Apple TV OS and XF iOS app)

@SotoiGhost
Copy link
Contributor

There could be a complex workaround for this, which is to remove the WebP part of one of the libraries but I'm not really sure if this will work. A solution could be updating SDWebImage to v5.x which removes the WebP part from their framework. I think we have the update task in our TODO list but we don't have an ETA for the release. If someone wants to update SDWebImage, Community PRs are very welcome! 😊

@adrianknight89
Copy link

I think we have the update task in our TODO list

@SotoiGhost Is this being tracked anywhere so we have more visibility?

@SotoiGhost
Copy link
Contributor

@adrianknight89 I think no, we haven't created any issue or task publicly.

@nmilcoff
Copy link

Is there any black magic like an mtouch argument that worths exploring? I have a similar situation, already tried --registrar:static and made sure all libs have SmartLink = true.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants