-
Hi! @asticode! Thank you for providing this excellent library! I would like to ask for advice regarding possible use of third-party built binaries of Background of the questionI am building on Windows. I am not very familiar with building Golang applications requiring C library dependencies, but I was able to set up MinGW-w64 and compile ffmpeg using your instructions provided in After some experimentation, I was also able to build an application using your library and the binary files from @GyanD ( However, the main issue with this approach is that @GyanD's binary distribution does not include I was able to circumvent this problem by taking the I understand that the problem with this approach is that it is not future-compatible, i.e. when you decide to update the version of ffmpeg supported by your library, new QuestionI'm sorry for a vague question, but I would like to ask if there could be any better solution to allow using your library with vendored binaries? I would greatly appreciate your advice 🙏 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
For reference, I would like to share the Makefiles that I came up with, which support both building (I am quoting only relevant parts, omitting some of the variable declarations which are not relevant to subject) Usage# Local build
make build-ffmpeg
# Download and prepare built binary files from gyan.dev
make get-gyan.dev-ffmpeg
# Build app with locally build ffmpeg libs
make FFMPEG_VER=n7.0 rebuild
# Build app with ffmpeg libs from gyan.dev
make rebuild Code
|
Beta Was this translation helpful? Give feedback.
-
Thing is, from Therefore unfortunately I don't see another option for you than providing the Also, if you build manually ffmpeg to get the |
Beta Was this translation helpful? Give feedback.
-
I'll consider including pc files with the next release. However, the prefix will need to be adjusted by the user. @asticode The rationale for a vendor build may be the third-party libraries linked. My full build referred to here has 80 external libs. |
Beta Was this translation helpful? Give feedback.
Thing is, from
go-astiav
's standpoint, usingpkgconfig
is the best way since it removes all the complexity of gathering all properCFLAGS
andLDFLAGS
forffmpeg
depending on the OS.Therefore unfortunately I don't see another option for you than providing the
pkgconfig
files 🤔 Apart from creating an issue in gyan.dev's repo to getpkgconfig
files in the releases.Also, if you build manually ffmpeg to get the
pkgconfig
files, why use the gyan.dev release? 🤔