Using Libraries in C++ (Static Linking)
ฝัง
- เผยแพร่เมื่อ 26 ก.ย. 2017
- Patreon ► / thecherno
Twitter ► / thecherno
Instagram ► / thecherno
Discord ► thecherno.com/discord
Series Playlist ► thecherno.com/cpp
Thank you to the following Patreon supporters:
- Samuel Egger
- Dominic Pace
- Kevin Gregory Agwaze
- Sébastien Bervoets
Gear I use:
-----------------
BEST laptop for programming! ► geni.us/pakTES
My FAVOURITE keyboard for programming! ► geni.us/zNhB
FAVOURITE monitors for programming! ► geni.us/Ig6KBq
MAIN Camera ► geni.us/t6xyDRO
MAIN Lens ► geni.us/xGoDWT
Second Camera ► geni.us/CYUQ
Microphone ► geni.us/wqO6g7K
Would love to see a video that explains "Make" files and using things such as CMake
That would be great, "Makefiles" are pretty complicated imho
@@groberti 100%
@@groberti Especially for beginners
I'm agree!! what if we don't use visual studio?
Would be great see how to do this with cmake
0:32 "its pretty simple!" said no CMake user ever!
@Spixmaster Pain in the ass for real
Lmao I feel you
...i just spent 2 hours messing with CMake. right in the feels
Make > CMake
Personal Notes:
- There are two parts in a library usually: includes and libraries. İnclude directory has a bunch of header files and lib directory has those pre-built binaries.
- Dynamic library is loaded(linked) into program at runtime, dynamic library can be anywhere and you do the linking whereas static library is put(compiled) into your executable program
- We have to point our compiler to header files (include files) and then we also have to point out our linker to library files.
And don't forget the library names :P
1:37 watching on a linux platform, a windows sound echoes
wtf?
he probably had his audio inputs a little messed up while he was recording the video, so his system audio got routed into the audio track in his video software :P
go home drunk, you are linux
yeah lol
lol
lol, yes
I'd be interested to see the "importing source code into another project in the same solution and compiling it to a static library" video.
redchant I second that!
redchant I third that
redchant I fourth that!
redchant I fifth that
I need this right now
I know I've probably already said this 100 times but thank you so much for all of your videos, they seriously help me so much. A lot of people who program aren't the best writers lol so it's really hard for me to follow along with most textbooks and written content from MIT, but watching you and hearing your clear explanations and SEEING how things work is so, so helpful, and makes it easier for me to code along with your examples (and pause the video to experiment if I have a "What if I do this?" moment) and to have it stick in my mind better
Great stuff as always , and yes linking libs from source code video would be a nice add to this series
The best playlist I've ever seen.. really detailed well.. keep up your videos and your way how to explain those complicated stuff really helpful.. thank mate
A really great thing about your video is that you not only tell us what and why to do, but also conduct those little experiments that deepen our understanding. Well done.
Amazingly detailed yet to the point. Thanks so much man
nothing clear than that.
the best c++ channel ever.
I love the idea of explaining with eye contact.
What a great video on this topic. Perfect explanation. Helps avoid a lot of pitfalls by understanding the steps. Thank you for sharing.
Coming from a GNU background I always found Visual Studio projects confusing to setup. This video cleared a lot of my confusion about using external libraries. Thanks!
Yeah, dealing with IDEs is always such a mess... the syntax highlighting is nice though. I find things like Sublime to be a nice middle ground.
Cherno, you are the only person that has made this make sense. You're an incredible teacher.
+1
1:37
Windows wants to tell you something.
no sound drivers, makes sense hehe
I thought it was the sound of my computer :>)
@Andrew Alfazy you didn't hear the ba dum tsss.
@Andrew Alfazy in plain 2018 Linux still hasn't got stable NVida support
You heard it too, hm?
great video. It often feels like so many other resources assume that one has this knowledge "a priori" and then you are stuck. You've shown that it is not that difficult, but one needs to learn it.
Wow this is amazing!!! I spent more than 8 hours trying to create libraries using the GLFW source code and Cmake. This was so much simpler, and he actually explained how the linkers work. Kudos to you man !!!
Anant Jain same ahaha
you find this simpler than using CMake? You’re out of your mind
@@mario_luis_dev No
I've been going through this series one video at a time, and it feels so rewarding to finally be covering libraries!
Thanks so much for this amazing walkthrough!
Oh my god thank you so much. This is exactly what I needed. I'm not used to using visual studio and I just wanted to compile using a library from a third party. Hooray!
First of, your videos are just the best I ever came across on C++ (atleast for me). And, love your long videos, please do more of in-depth. Learning a lot from you. Thanks
Your videos are very good and well presented. You have changed my view about C++. Thank you.
I really enjoyed this tutorial as always. However, I will say that I was pretty confused in the earlier parts of the video. I'd still consider myself kind of a beginner so when GLFW was brought up, I had to go on my own learning-tangent to find out what openGL and GLFW were.
Dude ..you are a dude of cpp...love to see your videos..i hated cpp but whenever i feel that way i watch your videos...and my perspective changes..👍
This one saved me, I was stuck for 2 weeks with the same linking error, thanks Cherno
I had to watch this video twice and read two articles to help, but now I fully understand thank you Cherno!
I'm definitely interested in building the source code for dependent libraries! Please make that video!
I think CMake videos would be super helpful for people on Linux and Mac. Thanks for the great content!
A really useful video. Thank you Cherno!
Very good video!
For the Linux users -
Static lib (".lib") is ".a" (Archive) in Linux and dynamic lib (".dll") is ".so" (Shared Object).
For MacOS dynamic libraries have the .dylib extension btw
Thank you for going in depth. I watch all your videos to the end.
i too they are simple and in depth
Love your videos brother!
Thank you very much for this video, it's help me find the way out, so awesome man!!!
You are awesome man. Was so confused about everything before watching this.
Great explanation, thank you. Despite years of coding in different IDEs and languages, I always got confused how to setup C and C++ projects in Visual Studio.
I used Visual Studio going way back into the early 1990s. No doubt, it is great in that it provides a lot of automation and help to get things done. It is the professional developer's choice for doing all kinds of projects. The thing is for beginners I would say using Eclipse is better because it is simpler and the developer has to understand what is actually going on.
1:00 i completely agree, i also hate linking 3rd libraries, but be careful to distribute other source code within your project repo, it might just go against their end user agreement
Nobody at university shows you this stuff. If I weren’t proactive in my studies I’d still be stuck writing cli programs. We’ve covered 3 languages and no one’s touched upon the topic of third party libraries. The closest we’ve gotten to an explanation was “just do ‘pip install’ and the manager will handle it” (python). No mention on basic stuff like having ‘requirements.txt’ or using virtual environments (especially on Linux).
So in conclusion: Thanks for the awesome videos! Really helpful
Man, this stuff is still confusing to me and I've had courses in C and C++. Thanks for the deep dives. I love it, and can't wait to start the Game Engine series.
Apart from the quality of the video, the like is for the statement "you should have everything you need, straightaway, to compile and run"! That's always a big hustle with github projects!
Another great video. Now I finally know the difference between static and dynamic libraries, and don't have to scratch my head haha.
Thanks!
More linking coming soon in the OpenGL series I'm assuming with GLAD. Good vid, thanks!
Loved the explanation
I programmed in c# the last 4 years but I still got stuck trying to transition to C++.
This video was clear and got me up and running. I wasted hours before I saw this and would have wasted more time if I hadn't seen this video.
I'm going to put the cherno on my tool bar.
Thanks a lot! You are so nice to listen to!
Pretty cool videos that you made. The only issue is the resolution of your screen (very high), however if the internet speed is slow it is difficult to view them in HD.
He kept that notification at 1:38 for the trolol xD
Goddamn I love you man :D best tutorial videos there are.
Please make a video on building from source! I'd love to see how you approach it! Most people I use use cmake
Oh God after some years of confusion with C++ Libraries finally a video that worths it. God thanks
Super good. Thanks.
"I just want things y work" oh, a man of culture, I see
Nice video, keep going! What is the brand of your watch???
Thans for the video! Finally I have found a clear explanation!
Very very good explanation!!!!
Really enjoying your videos. One question I have is when would I use a .def to specify exported functions? Are .def files still needed today?
Thank you very much. It is very useful.
this is the crap that hindering me from using c++ for years...i basically stuck with console apps...
@@SJKKA GL 😂👌
@@SJKKA use vs code, it is more transparent, you will learn a lot cuz you have to do it manually using .json files but it takes lot time. It took me 4 months.
@@xyz8206 How do you do it with .json files. Can you link an article or something?
Well done! Thank you!
In lesson 49, I finally understood the movement of the hand at the end of the video, this is in order to give high five to Cherno through the monitor))
very clear! thanks
Hi Cherno (Bill?). When you get to dynamic libraries in a future video, could you point out the differences between *nix and Windows in this regard. In particular why Linux likes things like theshared.so, theshared.so.1 and perhaps even theshared.so.0.1. Oh and there's ldconfig (?).
Keep up the great videos, you are very good at explaining things.
Yes please. Please go over linux dynamic linking. And maybe also other dynamic linking, such as in your own os.
Lookin' good Cherno!
Please do a day in a life of your daily work routine at ea or something similar! That would be amazing. Thanks
Watching this in 2020, but I believe this series will be around for many years to come.
Thanks that's really help me understand c++
Oh dude u make really good video
Thanks for doing this video. I was a pretty good C/C++ developer back in the 1990s and very early 2000s. Then I started to do lots of C#, Java, Web Dev, and database development. So after all that time I forgot some of the detailed nuts and bolts of where things go to do C/C++. Oh yeah, I remember now, LOL. Incidentally, after doing all that stuff for many years, I still like C/C++ the best.
For real. C/C++ and Java are pretty much the ancestors of programming today
You are awesome man!
thanks you helped me a lot
thank you for existing
i love you thanks for clearing everything up for me
Hi Mate, have watched a couple of your C++ videos. Very thorough. Though I'm running into trouble when trying to follow using Cross-Compile projects (Linux). When trying to set up a static library which cross-compiles along with multiple other C++ projects (Applications), I'm running into linking issues on the remote system. Do you think you can do a walkthrough using a remote linux machine for cross-compiling?
You're likely missing dynamic libraries on the remote system then that you are using in your build. The two main solutions are to either 1) install those dynamic libraries on the remote system and make sure they can be found (e.g. are in the environment's LD_LIBRARY_PATH
very awesome video。why can’t my visual studio(2019) add the dependent path of lib and .h files? it must use the full path.
You earned yourself a subscriber from me. Thank-you!
How and can i dynamically get a class from, with LoadLibrary loaded, function?
oh boi, helped me a lot, coding rust hack here. Using c++ and c#
I've had the link2019 error, solved that, but with Xenos injector i got error, cause its an external .lib so i going try add this to project, thx a lot for this video explanation about this subject.
So good!
Great video thxs
I got these errors:
· Warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; use /NODEFAULTLIB:library
· Error LNK2019: unresolved external symbol __imp__glClear@4 referenced in function _main
I managed to fix them going to *Properties > Linker > Input > Additional Dependencies* and adding
· opengl32.lib
Definitely want to hear about building libraries to link myself. I woul also like to hear about how the header files and linker work in the context of a binary. In your video on the linker, it worked very much hand-in-hand with the compiler, so if the compile step has already been completed for the binary, how does the linker know how to hook up both your binary and the already-compiled binary that you don't have the source for? Is there something in the header files that tells the linker what bits in the compiled binary correspond to which functions you would be calling out of it?
With symbols :P
Love to see if there is a tutorial on how to compile source code for library, perhaps in cmake?
so much thanks
A video documenting how to do this on other platforms would be great, say something like cmake if you were to build from source
Actually the version of visual studio a library was built with does matter because the binary may reference older SDK, linking to older libraries. And you might run into conflict issues when mixing different versions. It may work fine for some libraries like GLFW but it should in general case be discouraged. You'll know you're getting conflict errors in form of somewhat descriptive linker errors.
If the library API is only passing primitive types (int, bool, etc) then there shouldn't be an SDK conflict but if you have a library taking in anything from STD/STL as parameters or return values then the memory layout may have been changed across SDK versions.
Linux have bigger issues with binary compatibility model (linking to linux libraries) due to being updated so frequently, which is why the compile-it-yourself is so common on linux (apart from open source community).
Doesn’t work for glfw anymore, the glfw3.lib file isn’t static only anymore, apparently glfw3_mt.lib is the static build lib now
hello, I am enjoying your tutorials, but at 12:10 the include is showing me an error saying "cannot open source file GLFW/glf3.h" any help would be appreciated. the compiler error is C:\Users\Name\Desktop\CppDev\projects\ProjectSol\Project1\test.cpp(5,9): fatal error C1083: Cannot open include file: 'GLFW/glfw3.h>': No such file or directory
+The Cherno Well... there are reasons to use dynamic, including for security (update the lib in one place and the security patches will be there for everything linking it), and you also get reduced disk space usage overall for the system with this reuse. There are also some double edged swords. A bad update can break lots of code depending on it (experienced this on Arch Linux... bleeding edge indeed). I also sometimes deal with code with very specific dependencies and it is not fun hunting them all down to build a precise environment for ten different apps requiring three different Java versions... that's just gross and my life would be way easier if they statically linked their code. This is why for my own stuff I provide both static and dynamically linked versions (when possible, sometimes I have a dependency that doesn't build statically).
This is a simple problem to solve.
The Operating System is a base runtime that can run your programs. Every system package MUST be a closed circle, not linked to layers above, only below.
The user programs can use the system runtime libraries with dynamic linking, as the developer knows that the system WILL provide those libs in the correct version and location.
Every other lib that a program use that's not on the system runtime MUST be provided with the program, and used statically (even if using dynamic files) to avoid depending on the system repositories.
The system this way have a mission. Provide a SDK to build programs to run on it, and keep runtime compatibility with older versions, in a gap that can keep programs running at least for 10 years without recompiling.
This seems complicated, but actually is the simplest good way (not the simplest way ever) to do things.
Another more complex solution is to separate the system and the programs as two runtimes, and create symbolic links to specific lib versions that the programs need. If a program want x-1.0 then you instal x-1.0, but if another program wants x-1.6 then you install x-1.6, but as your programs will be looking for the same x lib, you create a symlink to the correct version that the program needs. This comes with the cost of keeping every single release of that lib on the repos, but as programs tend to use the latest version, the system can share a lot of code without breaking programs when updating.
@@talkysassis " the developer knows that the system WILL provide those libs in the correct version and location."
@@zvxcvxcz All of this only applies to servers. Windows, OSX ans Android have their stable runtimes.
You know what the runtime have. They don't break it on every new release.
very nice explanation i understood everything
I've started liking nuget packages in VS since it now supports native libraries.
Thank You!
very useful sir
Thank you for video.
Thank you!!!
do you know vcpkg? package manager made by microsoft for c++ . I think you should introduce it. I am using and it is very useful.
Very interesting video... Cherno !!
thank you very much
Hi Cherno, which library do you suggest that could do 3D （by x,y,z coordinates ）interpolation？
Hmm, this is mostly covering using a static library, but not to build your code statically. All sorts of fun issues one can run into there. Was just trying to static compile my program recently with GLEW and had -lGL in my g++ line... lol, of course that didn't work. And so I learned how to get g++ to compile just some dependencies manually (using '-Wl,' before the libraries you can to apply an option to and having that option be -Bstatic and -Bdynamic respectively. Like: g++ myprogram.cpp -o MyProgram -I someFolder -L somelibFolder -L someotherlibFolder -Wl,-Bstatic -lsomestaticlib -Wl,Bdynamic -lsomedynamiclib For those that aren't aware -lGL is provided by the GPU driver... so it's not going to be static or portable.
Some other things that aren't static build friendly: dlopen(), a lot of network libraries, e.g. curl.
Hey Cherno. I've recently made myself an opengl library that makes you write less repeating code. Currently I have the class specifications in the library's .h file and the class implementation in the .lib file. Is that the correct way of doing it, if not, how?
Please which video (about name mangling etc.) are you referring at 16:30? Thanks
Great video! What about the DLL file when running the compiled code? I usually add a post-script in VS and copy the DLL(s) to the output folder. Do have to keep in mind of which folder the executable is run from.
+Jostein Topland not applicable for this because we’re linking statically, there is no dll.
Yeah. I was thinking about dynamic linking. How do you deal with dependency DLLs in VS for that?
+Jostein Topland I try to deal with static libs whenever possible, but otherwise a post-build step to copy the dll is usually the way to go. You can use macros to make sure it ends up in the right place of course.
Sounds good. Due to the SDL 1.x LGPL license, linking has to be done dynamically, except if you include the SDL source code. For SDL2 zlib licence, static linking without including the SDL2 source code is fine. However, I see SDL2 projects still use dynamic linking. Do you have any opinions on dynamic vs static linking with SDL2?
Dynamic linking is fine, although there are other libraries (such as GLFW) which may be better suited depending on your needs, since SDL is a little heavy. As for SDL2, 100% static link. There's no benefit to dynamic linking.