/sci/ - Soyence and Technology

test

What do you need help with

best way to learn is by experience. just try to do as much as possible from the command line and eventually you'll be good.
obviously if you're super super new the first things you should learn are the very basics. like "touch", "nano", "cat", "cd", "ls", "rm", and anything else that lets you do basic operations with files from the CLI.
one utility i can recommend to you is "tldr". there are various implementations for it, personally i use tealdeer.
https://github.com/dbrgn/tealdeer
it basically tells you everything you need to know about a given command, and unlike man pages its actually very useful.

>>13583
man pages are helpful too tho, and universal.
This tool makes it quicker to get things done. No issue on that but if you find yourself on a remote server and you don't have the privileges to install packages like these it's a good idea to learn how to read man pages.

You can press "/" after opening a man page and search for a keyword.

>>13583
thanks a ton, 'teen
>>13563
i have no idea how to compile from git or from source or if those two things are even the same (some help would be appreciated)

>>13590
git is where you get source code, and source code is what you make programs in generally, usually the readmes have build instructions (compiling) where you navigate the terminal to the source code you got from git and compile (build) it into a program you can actually run by processing the source code into things your hardware can run in directly, most the time you just need to run make and the program developer already configured the makefile (what your compiler reads to know exactly how to build and install the program) but I've seen ones that use other tools, you can learn how to build something from code you got from some git repository using the included readme

>>13590
to expand on what the other 'teen said, make is used for C and C++ projects, software written in other languages requires you to launch other tools to compile them.
some dont require compilation at all if they're written in interpreted (as opposed to compiled) languages.
in general, the process to compile and install a program can vary a little bit from project to project, and usually the only important thing you need to know is that you'll find instructions on the README of the project (that text file you see when you open the page of a github project) or elsewhere on documentation you can find online

>>13594
also you should run 'ls' in your project directory first to check the build system, if there is a 'configure' script then you need to run that first (by entering "./configure") then make and if there is a autogen.sh script then you need to run that first then ./configure then make
some fags also use cmake (like dolphin-emu for example), you are going to have to check build instructions for this one (or try "cmake ." and check your luck)