Can't build Mac version #191

New Issue

claunia · 2026-01-29T16:37:30Z

claunia commented

2026-01-29 16:37:30 +00:00

Originally created by @mackworth on GitHub (Oct 10, 2016).

The github version does not compile; it complains about missing protobuf. I tried adding -I../src/ to the BLD_INCLUDE, and SRC_PROTOBUF="$(find ../src/protobuf-c -name '*.c')" to the BLD-SOURCES line, which avoids the error, but then it has the rather odd symptom of not producing an executable.

The 0.82 version downloaded from the original ccextractor site does compile and does work, but it seems to be behind the github version.

Originally created by @mackworth on GitHub (Oct 10, 2016). The github version does not compile; it complains about missing protobuf. I tried adding `-I../src/` to the BLD_INCLUDE, and `SRC_PROTOBUF="$(find ../src/protobuf-c -name '*.c')"` to the BLD-SOURCES line, which avoids the error, but then it has the rather odd symptom of not producing an executable. The 0.82 version downloaded from [the original ccextractor site](https://sourceforge.net/projects/ccextractor/?source=typ_redirect) does compile and does work, but it seems to be behind the github version.

claunia closed this issue

2026-01-29 16:37:30 +00:00

claunia commented

2026-01-29 16:37:31 +00:00

@cfsmp3 commented on GitHub (Oct 10, 2016):

Post the complete output from build so we can take a look.

On Mon, Oct 10, 2016 at 9:35 AM, Hugh Mackworth notifications@github.com
wrote:

The github version does not compile; it complains about missing protobuf.
I tried adding -I../src/ to the BLD_INCLUDE, and SRC_PROTOBUF="$(find
../src/protobuf-c -name '*.c')" to the BLD-SOURCES line, which avoids the
error, but then it has the rather odd symptom of not producing an
executable.

The 0.82 version downloaded from the original ccextractor site
https://sourceforge.net/projects/ccextractor/?source=typ_redirect does
compile and does work, but it seems to be behind the github version.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CCExtractor/ccextractor/issues/432, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFrJ2VsalisVBS7uwA7AgMQrKwYBzQUOks5qymlNgaJpZM4KSwek
.

@cfsmp3 commented on GitHub (Oct 10, 2016): Post the complete output from build so we can take a look. On Mon, Oct 10, 2016 at 9:35 AM, Hugh Mackworth notifications@github.com wrote: > The github version does not compile; it complains about missing protobuf. > I tried adding -I../src/ to the BLD_INCLUDE, and SRC_PROTOBUF="$(find > ../src/protobuf-c -name '*.c')" to the BLD-SOURCES line, which avoids the > error, but then it has the rather odd symptom of not producing an > executable. > > The 0.82 version downloaded from the original ccextractor site > https://sourceforge.net/projects/ccextractor/?source=typ_redirect does > compile and does work, but it seems to be behind the github version. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > https://github.com/CCExtractor/ccextractor/issues/432, or mute the > thread > https://github.com/notifications/unsubscribe-auth/AFrJ2VsalisVBS7uwA7AgMQrKwYBzQUOks5qymlNgaJpZM4KSwek > .

claunia commented

2026-01-29 16:37:32 +00:00

@mackworth commented on GitHub (Oct 10, 2016):

First is output without any changes:
ccextractor Build1.txt

Then I changed build.command to:
build2.command.txt

and got essentially the same results without the protobuf errors, but with no binary!
ccextractor build2.txt

I should mention that many of the warning messages from clang should probably be looked into. It looks like several checks are not doing what they look like they're doing due to type issues.

Oh, and here's the output from the (successful) sourceforge version 0.82
ccextractor sourceforge.txt

@mackworth commented on GitHub (Oct 10, 2016): First is output without any changes: [ccextractor Build1.txt](https://github.com/CCExtractor/ccextractor/files/520031/ccextractor.Build1.txt) Then I changed build.command to: [build2.command.txt](https://github.com/CCExtractor/ccextractor/files/520032/build2.command.txt) and got essentially the same results without the protobuf errors, but with no binary! [ccextractor build2.txt](https://github.com/CCExtractor/ccextractor/files/520037/ccextractor.build2.txt) I should mention that many of the warning messages from clang should probably be looked into. It looks like several checks are not doing what they look like they're doing due to type issues. Oh, and here's the output from the (successful) sourceforge version 0.82 [ccextractor sourceforge.txt](https://github.com/CCExtractor/ccextractor/files/520061/ccextractor.sourceforge.txt)

claunia commented

2026-01-29 16:37:32 +00:00

@cfsmp3 commented on GitHub (Oct 11, 2016):

Most likely you also have to add curl to the list of libraries.

@cfsmp3 commented on GitHub (Oct 11, 2016): Most likely you also have to add curl to the list of libraries.

claunia commented

2026-01-29 16:37:32 +00:00

@mackworth commented on GitHub (Oct 11, 2016):

Figured this one out; I missed an error message for utf8proc buried in all the warnings. I'll do a pull request for the revised build command that incorporates protobuf and utf8proc in the process.

@mackworth commented on GitHub (Oct 11, 2016): Figured this one out; I missed an error message for `utf8proc` buried in all the warnings. I'll do a pull request for the revised build command that incorporates protobuf and utf8proc in the process.

claunia commented

2026-01-29 16:37:33 +00:00

@mackworth commented on GitHub (Oct 11, 2016):

fixed in PR #435

@mackworth commented on GitHub (Oct 11, 2016): fixed in PR #435

claunia referenced this issue

2026-01-29 16:58:59 +00:00

[PR #191] [MERGED] Making Demuxer Context #1073

Sign in to join this conversation.