-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sharedlib fails #3
Comments
We normally build on Mac OS and on Linux (debian via Docker)... are you on
Windows? It hasn't been exercised much.
…On Wed, Oct 2, 2019 at 4:53 PM WildTV ***@***.***> wrote:
make: *** No rule to make target 'sharedlib'. Stop.
Seems the root Makefile has sharedlib, but the Makefile in src has nothing
to reference sharedlib and thus fails. ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=ABC5NBO6TQGKDXDET7AKYVTQMUQ7BA5CNFSM4I44K33KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HPIK2KA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABC5NBM5X7MF5K62445G5NDQMUQ7BANCNFSM4I44K33A>
.
|
-Edit, wrong machine |
Here's s a small Dockerfile that attempts to build on a clean debian:8 (jessie) image:
This works fine when using
Looks like one of the libraries caption-inspector depends on (libswresample) is not supported in Jessie: https://packages.debian.org/search?keywords=libswresample-dev |
After looking at the build/ffmpeg requirements, I'll probably end up using the docker package on the end goal target, Stretch. I just tried building at the end of the day on my desktop and got that error when trying to build the binding portion, the application appears to have built fine otherwise.
Tried on the home machine, same deal, but stretch. Maybe I'm just an idiot ;) |
Already built by |
make: *** No rule to make target 'sharedlib'. Stop.
Seems the root Makefile has sharedlib, but the Makefile in src has nothing to reference sharedlib and thus fails. ?
The text was updated successfully, but these errors were encountered: