-
Notifications
You must be signed in to change notification settings - Fork 440
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of https://github.com/CCExtractor/ccextractor i…
…nto qualip-ocr_bitmap-last_font_tag
- Loading branch information
Showing
82 changed files
with
15,638 additions
and
1,248 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
name: Unit Test Rust | ||
on: | ||
push: | ||
paths: | ||
- ".github/workflows/test.yml" | ||
- "src/rust/**" | ||
tags-ignore: | ||
- "*.*" | ||
pull_request: | ||
types: [opened, synchronize, reopened] | ||
paths: | ||
- ".github/workflows/test.yml" | ||
- "src/rust/**" | ||
jobs: | ||
test_rust: | ||
runs-on: ubuntu-latest | ||
defaults: | ||
run: | ||
working-directory: ./src/rust | ||
steps: | ||
- uses: actions/checkout@v4 | ||
- name: cache | ||
uses: actions/cache@v4 | ||
with: | ||
path: | | ||
src/rust/.cargo/registry | ||
src/rust/.cargo/git | ||
src/rust/target | ||
src/rust/lib_ccxr/target | ||
key: ${{ runner.os }}-cargo-${{ hashFiles('**/Cargo.lock') }} | ||
restore-keys: ${{ runner.os }}-cargo- | ||
- uses: actions-rs/toolchain@v1 | ||
with: | ||
toolchain: stable | ||
override: true | ||
- name: Test main module | ||
run: cargo test | ||
working-directory: ./src/rust | ||
- name: Test lib_ccxr module | ||
run: cargo test | ||
working-directory: ./src/rust/lib_ccxr |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# CCExtractor Docker image | ||
|
||
This dockerfile prepares a minimalist Docker image with CCExtractor. It compiles CCExtractor from sources following instructions from the [Compilation Guide](https://github.com/CCExtractor/ccextractor/blob/master/docs/COMPILATION.MD). | ||
|
||
You can install the latest build of this image by running `docker pull CCExtractor/ccextractor` | ||
|
||
## Build | ||
|
||
You can build the Docker image directly from the Dockerfile provided in [docker](https://github.com/CCExtractor/ccextractor/tree/master/docker) directory of CCExtractor source | ||
|
||
```bash | ||
$ git clone https://github.com/CCExtractor/ccextractor.git && cd ccextractor | ||
$ cd docker/ | ||
$ docker build -t ccextractor . | ||
``` | ||
|
||
## Usage | ||
|
||
The CCExtractor Docker image can be used in several ways, depending on your needs. | ||
|
||
```bash | ||
# General usage | ||
$ docker run ccextractor:latest <features> | ||
``` | ||
|
||
1. Process a local file & use `-o` flag | ||
|
||
To process a local video file, mount a directory containing the input file inside the container: | ||
|
||
```bash | ||
# Use `-o` to specifying output file | ||
$ docker run --rm -v $(pwd):$(pwd) -w $(pwd) ccextractor:latest input.mp4 -o output.srt | ||
|
||
# Alternatively use `--stdout` feature | ||
$ docker run --rm -v $(pwd):$(pwd) -w $(pwd) ccextractor:latest input.mp4 --stdout > output.srt | ||
``` | ||
|
||
Run this command from where your input video file is present, and change `input.mp4` & `output.srt` with the actual name of files. | ||
|
||
2. Enter an interactive environment | ||
|
||
If you need to run CCExtractor with additional options or perform other tasks within the container, you can enter an interactive environment: | ||
bash | ||
|
||
```bash | ||
$ docker run --rm -it --entrypoint='sh' ccextractor:latest | ||
``` | ||
|
||
This will start a Bash shell inside the container, allowing you to run CCExtractor commands manually or perform other operations. | ||
|
||
### Example | ||
|
||
I run help command in image built from `dockerfile` | ||
|
||
```bash | ||
$ docker build -t ccextractor . | ||
$ docker run --rm ccextractor:latest --help | ||
``` | ||
|
||
This will show the `--help` message of CCExtractor tool | ||
From there you can see all the features and flags which can be used. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
FROM alpine:latest as base | ||
|
||
FROM base as builder | ||
|
||
RUN apk add --no-cache --update git curl gcc cmake glew glfw \ | ||
tesseract-ocr-dev leptonica-dev clang-dev llvm-dev make pkgconfig \ | ||
zlib-dev libpng-dev libjpeg-turbo-dev openssl-dev freetype-dev libxml2-dev | ||
|
||
RUN cd && git clone https://github.com/gpac/gpac | ||
WORKDIR root/gpac/ | ||
RUN ./configure && make && make install-lib && cd && rm -rf /root/gpac | ||
|
||
WORKDIR /root | ||
RUN git clone https://github.com/CCExtractor/ccextractor.git | ||
RUN apk add bash cargo | ||
RUN export LIB_CLANG_PATH=$(find / -name 'libclang*.so*' 2>/dev/null | grep -v 'No such file' | head -n 1 | xargs dirname) | ||
RUN cd /root/ccextractor/linux && ./pre-build.sh && ./build | ||
|
||
RUN cp /root/ccextractor/linux/ccextractor /ccextractor && rm -rf ~/ccextractor | ||
|
||
FROM base as final | ||
|
||
COPY --from=builder /lib/ld-musl-x86_64.so.1 /lib/ | ||
COPY --from=builder /usr/lib/libtesseract.so.5 /usr/lib/ | ||
COPY --from=builder /usr/lib/libleptonica.so.6 /usr/lib/ | ||
COPY --from=builder /usr/local/lib/libgpac.so.12 /usr/local/lib/ | ||
COPY --from=builder /usr/lib/libstdc++.so.6 /usr/lib/ | ||
COPY --from=builder /usr/lib/libgcc_s.so.1 /usr/lib/ | ||
COPY --from=builder /usr/lib/libgomp.so.1 /usr/lib/ | ||
COPY --from=builder /usr/lib/libpng16.so.16 /usr/lib/ | ||
COPY --from=builder /usr/lib/libjpeg.so.8 /usr/lib/ | ||
COPY --from=builder /usr/lib/libgif.so.7 /usr/lib/ | ||
COPY --from=builder /usr/lib/libtiff.so.6 /usr/lib/ | ||
COPY --from=builder /usr/lib/libwebp.so.7 /usr/lib/ | ||
COPY --from=builder /usr/lib/libwebpmux.so.3 /usr/lib/ | ||
COPY --from=builder /lib/libz.so.1 /lib/ | ||
COPY --from=builder /lib/libssl.so.3 /lib/ | ||
COPY --from=builder /lib/libcrypto.so.3 /lib/ | ||
COPY --from=builder /usr/lib/liblzma.so.5 /usr/lib/ | ||
COPY --from=builder /usr/lib/libzstd.so.1 /usr/lib/ | ||
COPY --from=builder /usr/lib/libsharpyuv.so.0 /usr/lib/ | ||
|
||
COPY --from=builder /ccextractor / | ||
|
||
ENTRYPOINT [ "/ccextractor" ] | ||
|
||
CMD [ "/ccextractor" ] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,71 @@ | ||
# C to Rust Migration Guide | ||
|
||
## Porting C Functions to Rust | ||
|
||
This guide outlines the process of migrating C functions to Rust while maintaining compatibility with existing C code. | ||
|
||
### Step 1: Identify the C Function | ||
|
||
First, identify the C function you want to port. For example, let's consider a function named `net_send_cc()` in a file called `networking.c`: | ||
|
||
```c | ||
void net_send_cc() { | ||
// Some C code | ||
} | ||
``` | ||
|
||
### Step 2: Create a Pure Rust Equivalent | ||
|
||
Write an equivalent function in pure Rust within the `lib_ccxr` module: | ||
|
||
```rust | ||
fn net_send_cc() { | ||
// Rust equivalent code to `net_send_cc` function in `networking.c` | ||
} | ||
``` | ||
|
||
### Step 3: Create a C-Compatible Rust Function | ||
|
||
In the `libccxr_exports` module, create a new function that will be callable from C: | ||
|
||
```rust | ||
#[no_mangle] | ||
pub extern "C" fn ccxr_net_send_cc() { | ||
net_send_cc() // Call the pure Rust function | ||
} | ||
``` | ||
|
||
### Step 4: Declare the Rust Function in C | ||
|
||
In the original C file (`networking.c`), declare the Rust function as an external function: | ||
|
||
```rust | ||
extern void ccxr_net_send_cc(); | ||
``` | ||
|
||
### Step 5: Modify the Original C Function | ||
|
||
Update the original C function to use the Rust implementation when available: | ||
|
||
```c | ||
void net_send_cc() { | ||
#ifndef DISABLE_RUST | ||
return ccxr_net_send_cc(); // Use the Rust implementation | ||
#else | ||
// Original C code | ||
#endif | ||
} | ||
``` | ||
|
||
## Rust module system | ||
|
||
- `lib_ccxr` crate -> **The Idiomatic Rust layer** | ||
|
||
- Path: `src/rust/lib_ccxr` | ||
- This layer will contain the migrated idiomatic Rust. It will have complete documentation and tests. | ||
|
||
- `libccxr_exports` module -> **The C-like Rust layer** | ||
|
||
- Path: `src/rust/src/libccxr_exports` | ||
- This layer will have function names the same as defined in C but with the prefix `ccxr_`. These are the functions defined in the `lib_ccx` crate under appropriate modules. And these functions will be provided to the C library. | ||
- Ex: `extern "C" fn ccxr_<function_name>(<args>) {}` |
Oops, something went wrong.