about the dll
|
2014-10-29, 04:51 PM
|
|||
|
|||
about the dll
There is something I'd like to know about the dynamic libraries : what make a function or a variable will be supposed to be in a such library and not in the main executable ?
They was confident : "Only some thousands of bricks, and it will look like something !"
More a community is little, more the "others will do it" way to think is dangerous for it. |
|||
2014-10-29, 05:26 PM
|
|||
|
|||
RE: about the dll
For most projects, functions and variables from a different project will be in a .dll instead of the .exe.
Best regards,
Victor //victorz.ca Code: Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|) |
|||
2014-10-30, 03:53 AM
|
|||
|
|||
RE: about the dll
It isn't what I mean.
When a compiler make a new executable, it need to know what will be in this executable and what will be found in a dll. I mean what in the code make the compiler knows if a function or a variable will be or not in the executable and, if not, what will be the name of the dynamic library where find it ? They was confident : "Only some thousands of bricks, and it will look like something !"
More a community is little, more the "others will do it" way to think is dangerous for it. |
|||
2014-11-02, 10:59 AM
|
|||
|
|||
RE: about the dll
I think source/lib contains .lib files, which can be for both static and dynamic libraries.
Best regards,
Victor //victorz.ca Code: Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|) |
|||
2014-11-02, 02:46 PM
|
|||
|
|||
RE: about the dll
Theorically, MinGW don't use .lib files, the problem must be in the .a files I downloaded.
They was confident : "Only some thousands of bricks, and it will look like something !"
More a community is little, more the "others will do it" way to think is dangerous for it. |
|||
2014-11-09, 11:53 AM
(This post was last modified: 2014-11-09, 11:54 AM by Victor.)
|
|||
|
|||
RE: about the dll
In order "to link some code against a DLL (on Windows), you have to link against a .lib file [...] On Unix [...], there is no need for such wrappers (the linker is smart enough to generate them on the fly)".
Also, .a seems to be for Linux while .lib is for Windows, so I'm not sure about how to use .dlls with .a files. Best regards,
Victor //victorz.ca Code: Your antithesis compares favorably with any high magnitude of pwnage. (-you > |p|, you < -|p|) |
|||
« Next Oldest | Next Newest »
|