35b4c181b3
This option will build four executables: - dropout-dl-minimal (with curl without sqlite or gcrypt) - dropout-dl-sqlite (with curl and sqlite without gcrypt) - dropout-dl-full (with curl, sqlite and gcrypt) - tests |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
src | ||
tests | ||
.gitignore | ||
CMakeLists.txt | ||
LICENSE | ||
readme.md |
readme.md
dropout-dl
A tool to download dropout.tv episodes.
How to Build
cmake -S <source-dir> -B <build-dir>
cd <build-dir>
make
Dependency Installation
sqlite-devel is optional with the use of the --force-cookies
option but this is not recommended.
Void
sudo xbps-install -S libcurl sqlite-devel
Debian
sudo apt install libcurl4-gnutls-dev sqlite-devel
Cookies
Firefox
Create a file named firefox_profile
in the build directory and paste in your firefox profile folder path
Chrome
Install libgcrypt and create a file named chrome_profile
in the build directory and paste in your chrome profile folder path (found on chrome://version)
Other/No Sqlite
Use the --force-cookies
program option to manually input cookies.
How to Use
./dropout-dl <url> [OPTIONS]
By default, dropout-dl will download the episode in the format <series>/S<season-num>E<episode-num><name>.mp4
Options
--help Display this message
--quality Set the quality of the downloaded video. Quality can be set to 'all' which
will download all qualities and place them into separate folders
--output Set the output filename
--output-directory Set the directory where files are output
--verbose Display debug information while running
--force-cookies Interpret the next to arguments as authentication cookie and session cookie
--series Interpret the url as a link to a series and download all episodes from all seasons
--season Interpret the url as a link to a season and download all episodes from all seasons
TODO
- Create tests
- Handle non-alphanumeric characters
- Test build process on other setups with other OSs.
Contributing
Issues
If you have any issues or would like a feature to be added please don't hesitate to submit an issue after checking to make sure it hasn't already been submitted. Using the templates is a good place to start, but sometimes they're overkill. For example, if the program segfaults for you, you don't need to state that the intended behaviour is to not segfault.
If you'd like to contribute a good place to start is looking at open issues and trying to fix one with a pull request.
Working on your first Pull Request? You can learn how from this free series How to Contribute to an Open Source Project on GitHub
Contributors
- Moss - mossx-dev