🏗️ Build your libraries easier using build systems

  Рет қаралды 1,701

Code for yourself

Code for yourself

Күн бұрын

Пікірлер: 10
@CodeForYourself
@CodeForYourself 2 жыл бұрын
What build system are you most interested in? Which one do you hear most about?
@andreibaraian88
@andreibaraian88 2 жыл бұрын
Cmake and bazel
@bsdooby
@bsdooby 2 жыл бұрын
CMake for the win.
@masaaldosey
@masaaldosey 2 жыл бұрын
Interested in CMake :D
@coolguy69235
@coolguy69235 2 жыл бұрын
Interested in Bazel / ninja build systems
@princepatel_channel
@princepatel_channel 2 жыл бұрын
+1 for Bazel
@ahans123
@ahans123 2 жыл бұрын
Mentioning Bazel and Ninja in the same sentence is a bit odd IMHO. With Bazel actually aiming to do everything itself, while Ninja is a build backend that is supposed to its input files generated. I suppose you're going for CMake generating a Ninja build, which is probably a good approach for this series. After all, CMake is probably the most commonly used build tool for C++. However, I've grown quite fond of Bazel in recent years, so giving an overview there would probably be very useful!
@CodeForYourself
@CodeForYourself 2 жыл бұрын
Hey Alex, well, I wouldn't say it's that odd to be honest 🤷. I might, of course, be wrong here, but Ninja is really closest to Make in my view. It is a simple script of dependencies and commands to build them, so in the end it just calls your compiler with certain inputs in a certain sequence. Bazel is not really that much different. It does, of course, a lot more and provides a more abstract way of designing ones build but essentially it still comes down to calling your compiler with a certain set of flags in a certain order. So from this perspective Bazel, Make and Ninja do the same. CMake on the other hand _does not_ call the compiler on its own. It generates the Makefile or a ninja build file (or others) and that's about it. In the next step, the underlying build system still has to be called to actually call the compiler program with the needed inputs. I think the reason why it feels odd is that people keep talking about CMake and Bazel as an "end-to-end" system, while they rarely do so about Make and Ninja and I give you that. But I hope that my logic is not too flawed either. Anyway, we're gonna be using CMake + Make combination in the course as a basis but after that people should have zero issues replacing Make with ninja if they want. Sorry for a lengthy answer :)
@ginsonmathew186
@ginsonmathew186 2 жыл бұрын
+1 for bazel
@piperosgr
@piperosgr 2 жыл бұрын
let's do bazel
CMake - the essential package
27:54
Code for yourself
Рет қаралды 12 М.
Why use templates in modern C++
12:32
Code for yourself
Рет қаралды 2,2 М.
If people acted like cats 🙀😹 LeoNata family #shorts
00:22
LeoNata Family
Рет қаралды 35 МЛН
Правильный подход к детям
00:18
Beatrise
Рет қаралды 1,7 МЛН
Learn Bash Basics
22:27
James Champion
Рет қаралды 1,6 М.
Master Pointers in C:  10X Your C Coding!
14:12
Dave's Garage
Рет қаралды 330 М.
My Forever Dev Workflow
16:02
typecraft
Рет қаралды 109 М.
Every Programming Language Ever Explained in 15 Minutes
15:29
Flash Bytes
Рет қаралды 357 М.
Writing My Own Database From Scratch
42:00
Tony Saro
Рет қаралды 258 М.
A New Era for C and C++? Goodbye, Rust?
9:08
Travis Media
Рет қаралды 91 М.
Assembly Basics: The Language Behind the Hardware
12:55
WhiteboardDoodles
Рет қаралды 31 М.
Don't use static (outside of classes) in modern C++
15:56
Code for yourself
Рет қаралды 6 М.