How do you handle external libraries on a GitHub repo? Especially if they're huge, like 150+ MB?

How do you handle external libraries on a GitHub repo? Especially if they're huge, like 150+ MB?

Don't most people just write a build in the README.txt file?

You write an ebuild

Just list your dependancies in the README man. Not that hard. Also, be sure to document the build process WELL, as in THOROUGHLY WELL, otherwise its sickening tiresome retardation which no one will want to try again

Bullshit
Fork it, don't change it. Include the build script into your main one.

Like describe the build process?

I have a quite practical problem. Most of the libs I use are on my drive under C:\dev (yeah, haha, windows, etc).

For example C:\dev\wxWidgets or C:\dev\zlib

My project links to several of these. So I was thinking either I put all those under /ext/ in the project folder, which would make the repo huge, or I write up some kind of step by step build process. But do I just write "put these libs under C:\dev" or what? Seems oddly demanding.

How do other projects solve this?

>C:\
Begone, wincuck.

Ask the user to install it themselves before building your project, provide the names of your dependency libraries and preferably the version numbers you support.

git submodules

>caring about what OS someone else uses

/thread

Dayum. I don't about advice for that

If you're using something like a makefile as your build tool you'd put a variable at the start containing the path to the library and then use that variable in your actual commands. Then you'll mention that users need to set that variable in your readme.

If you're using visual studio or something I don't know what deal is though.

Enjoy no package repo or a package manager, wincuck lmfao

you put them in package.json or requirements txt and then
npm install


or

pip install -r requirements.txt


i'm sure rust and other modern languages worth their salt have mechanisms for automatic dependency downloading too. if a language doesnt have this rudimentary feature, it's not worth using.

Thanks, that actually makes a lot of sense.

>tfw C++ cuck because I need to use Qt

Just make it a submodule you fuck

>you'd put a variable at the start containing the path to the library and then use that variable in your actual commands. Then you'll mention that users need to set that variable in your readme.
lol, what retarded language requires you to manually download dependencies and change shit in text files to even run it?
i thought at this point all languages have something that lets you build and start a project with one command

>what are project versions
>what are obscure libs no one uses
>what are forks
If you think you can generalize all that shit, good fucking luck

Struggles of Cniles

> huge
> 150+mb
Pick one

>app is 0.1 MB
>dependencies are 150MB
It's all relative user