Static vs. Shared Libraries
ฝัง
- เผยแพร่เมื่อ 16 เม.ย. 2016
- Static vs. Shared Libraries
Instagram: / davex.tech
Home: davidxiang.com
Book: www.amazon.com/dp/B07D5QNGVZ
Facebook Page: / davex.tech
Twitter: / davex_tech
Email: davex.inc@gmail.com
#software #coding #softwaredevelopment #programming #howtocode - วิทยาศาสตร์และเทคโนโลยี
![[Watch Party] APL 2024 Bacon Time Vs Hong Kong Attitude ชนะเข้ารอบ](http://i.ytimg.com/vi/ikUfW81sDaw/mqdefault.jpg)
Another pro to Dynamic Libraries is that they are Shared Libraries. If you have 80 different applications that depend on the dynamic library, they all call the same DLL at run time. They are SHARING the library. You do not have duplication of the library's code, and each executable only contains it's own code. This is why Dynamic Libraries are called Shared Libraries.
thank you master
You might've done this 6 years ago, but this is so well explained. You've just earned one more subscriber.
Keep making the tech videos for noob like me. much appreciated
+1 noob
You making this specific video is a good example of why the internet is so great! Thank you, glad you decided to talk about this. I've seen .dll files many times over the years, never knew (nor was curious to know) what they were.
Real good stuff! Feels good to get the feel of how things work under the hood in general. Keep more such videos coming!
Hey Dave, I hope you can keep making these tech videos. I played this video during one of my college's C# classes, and everyone in the class loved it. Hope you can keep making more, they're super useful and will make for a wonderful reference in the future to come back to!
Nice! haha wow that's cool. Yea, I haven't made a technical video in awhile, I'll have to make one
Hands down best explanation of static and shared libraries. I much needed this video as I was struggling to understand this concepts.
Keep making the tech vids. We love it
Dave! You should keep making the tech videos. The simplicity of your explanation is splendid.
I started watching your videos on sunday morning, when I was hungover ... that day changed my life... 😊
This is the best explanation ive come across so far. Thanks!
Subscribed! You are better at explaining these concepts than any professor I've ever had.
Thank you for another great video Dave. Keep´em coming :)
you are so good at explaining things！thanks Dave
Thanks for making this, very useful. We need more fundamentals like this
Really dig your style of explanation. So calm and measured. I understood all of it. Thanks!
This explanation was pretty much perfect. Thank you!
Great video man, brilliant tone and explanation flow.
Really good and simpler explanation. Thank you so much for this video. Subscribed !
Great video. I now understand static and shared libraries more vividly. Thank you.
thank you so much for those explanations. subbed!!!
I love how much easy you made understanding this concept. God bless you
Me caiste bien amigo.
Explicas de una manera espectacular, seguire viendo todos tus videos.
Gracias
Extremely thankful to you Dave!!...You explained such a complex things in such an easygoing way..keep making the tech videos🔥
I agree
Thanks for the video, it's very educational! I also laughed a little when you told us about how you messed with some of the .dll files on your computer can bricked it as I also did that when I was a kid (was my first time seeing a blue screen).
You explained this topic beautifully, very clear and precise. Thanks Dave.
Outstanding Explanation Dave Xiang..
Your explanation about compile time versus run time loading of static library and shared library, respectively, was good.
Thanks man, keep up the good work!
I'm not learning any C-like languages (yet), but this helped me better understand what's going on when I have dependency issues of any sort, whether it's managing language versions, getting frameworks up and running, linux stuff, etc. This also clarified some differences between "compile-time" and "runtime". Thx!
+James Gaehring glad it was helpful! thx
Thanks Very much for this talk on libraries - you have touched on some cool points.
10 minutes well spent thanks buddy
dave Xiang is the man!!!! your videos are helping
So who told you your videos on tech are shitty? This is the information I've spent close to 72 hours sourcing for. Great job!
You have a really good accent. Simple and strait forward, Keep making tech videos for us! lol!!
this has helped me so much! thank you! really appreciate it.
Thank you for this video, you explained chapter 1 of my linux+ book very well!
I really love this video! Detailed explanation, you broke things down to the core.
Thank you very much😃, I really enjoyed it👍
Thanks Dave Xiang - very good explanation .
Great way of explaining it, thanks for video!
Thank you so much for the introduction.
You explained that very well. Thanks!
I finally found you - - This is really good
David, Im extremely grateful for what youre doing here for the newbie community. im about to undergo a web app development curriculum that stresses a slow path.. and their language of choice to teach is Ruby. do you have any opinions about Ruby as a first language?
Ruby is a good first language for sure. Easy to write, easy to understand. Also, very popular with web programming.
Hello , I know it's been 7 YEARS, but in the Event that you see this, how did that curriculum workout for you?
Thank you for explaining this so well.
Thank you! This is a great supplementary video to LFS201.
Learnt great stuff from your video that I was not able to answer in one of my interview and failed.. Thanks alot for such kind of stuff :)
You explain things very well!
Cool explanation, thank you very much!
Yeah Thank you, this is very concise explanation and cleared my doubts, which I didn't know to form a query to Google search.
As a typical highly interested in the why of stuff. I was looking in my systems and was like ..shared storage my ass... then I cancel the clear data . I came to this and wow. You do really great at teaching. I am not in this field of expertise but l can say this...I understand a whole lot more about my phone now.
You guys use us being connected so we help give strength to the core of this huge web of shared storage...interesting.
That's kind of cool .
what programming or developing... I think this was a good video. Dont ever give up or not do your desire. Tech is in need of your communication style. Keep up on this stuff.
great conceptual explanation of it!
excellent tutorials....i just love it...keep it up
Great explanation. Thanks for sharing!
This video is 7 years old and it aged so well even now
Very well explained. Thanks a lot!
Very good and simple explanation. Easy to understand.
Thanks for the great videos. Your videos gave a clear picture of what's going on under the hood..
Can you please make a video on how linkers work, what are relocatable object codes and some info on symbol table in context of C program compilation.
Thanks Dave!
Subscribed after this
Very nice video.. Tech videos rock!
Great Video!!! Thank you, keep on please
keep making tech videos :) & thanks for helping me
Super helpful. Thanks man!
Great explanation man, thank you
Just to sum up using code:
file.c
#include
int main(){
printf("Hello");
}
If we compile this file using gcc then there are two ways either we use shared library to include printf() functionality or we use static library which include whole other bunch of function along with pritnf() which make our executable heavy...
Simplely compile your above program in two ways:
gcc -o output file.c
gcc -o output2 -static file1.c
And check the size of output and output2. Since output2 is statically compiled it size is greater then output file.
very well explained, thank you very much.
really solid explanation!
that was a very good explanation.
thank you.. learnt alot ❣️
Thanks a lot for this !
Man, don't care too much about views for any given video. Technical videos are much appreciated and you help a lot of people.
awesomeness ... 👌👌👌👌 please continue making these tech videos... I'm finally understanding coding ..... thanks a lot !! please do complete tutorials on c# ....
Great video, i understand clearly
yes ! for me very helpful and understandable video.. thank you for sharing ...
Excellent explanation.
+Dave Xiang I've recently discovered you channel, and I think it's one of the best of its genre. Thanks a lot for all the knowledge! I would really like if you could answer one question I have: I'm currently learning C (as a first language) on Linux, and I'm reading Stephen Prata's C primer plus. Should I continue reading it, or do you recommend me another book/course?
+Lucio Cardoso Nice! C is an ambitious language to learn first but should be fruitful once you understand it. I don't know about that book personally, but just make sure you can differentiate from a "reference" style vs "curriculum" style book. I would get one for each. A curriculum you can easily follow, and a reference which you can index for specifics.
I REALLY like the tech videos.
Thank you!!!
Thanks for the video
dang! that's a headshot of explanation!
I use static libraries when there is less duplicated code to not worry about run time dependencies, but if I have some code that most of the rest of my project(s) need, I bung it in a shared library.
THANK YOU!
Awesome .... thankyou so much
good explanation, keep it up!
subscribed
after this
sounds like for smaller applications at least (that use few libraries) static libraries is the way to go unless its libraries that you can almost garantee is already something the end user is using anyways.
printing to console would be a good shared.
but
a highly customized graphics library might be better off as static.
Awesome, Thanks
It's a nice overview about these types of libraries, but you tend to repeat your structure sometimes.
Can you make a video on how to link to the boost library, and perhaps how to use CMake in the terminal to do all that?
Awesome, Do you know any book that explains libraries in details? I'm learning programming and I find this topic very confusing.
Thanks! this is helpful
Thank you man.
Really it's simply an awesome stuff..
Keep Going!
amaaaaaaaaaaaazing thx dave !!!!
very informative thanks a lot.
Hey Dave, great video! I had a quick question. In C, when you do #Include to get the printf function, would this be "static" since the preprocessor does a literal copy and paste of that entire stdio.h file on top of my other source code? if so, what would be an example of dynamic linking? Thanks again!
when you do the #include you get a copy and paste of the header file. you still need to link w/ the implementations. you have a choice of dynamic vs static even for standard library just as you would custom library. most often, depending on OS and compiler defaults, the standard libraries will be a shared lib on the system somewhere. Like a library like... /lib/libc.so (something like that) Don't quote me on that, but you'll have the option of doing both. If you really want, you can also statically link contents from the standard lib into your executable.
Although I might be wrong, but actually there is small mistake in your explanation. All the executable code or implementation of functions in particular library (at least in case C and C++) lies in DLL files. Bit in static linking of library in time of compilation a .lib file is used to find a needed function in DLL file, while in dynamic linking the process differs and a .lib file is not needed.
So .lib files are for the static linking, but the actual code of library are contained in dll file in both cases.
Its info on WIki:
en.wikipedia.org/wiki/Dynamic-link_library
Really helpful , Thanks :)