Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/paramsiddharth/c-linking-libraries
Linking libraries in C, statically and dynamically.
https://github.com/paramsiddharth/c-linking-libraries
Last synced: about 1 month ago
JSON representation
Linking libraries in C, statically and dynamically.
- Host: GitHub
- URL: https://github.com/paramsiddharth/c-linking-libraries
- Owner: paramsiddharth
- Created: 2021-05-29T05:35:33.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-05-29T07:35:47.000Z (over 3 years ago)
- Last Synced: 2024-05-22T20:22:57.517Z (7 months ago)
- Language: Makefile
- Size: 15.6 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Linking Libraries in C
Examples of static and Dynamic linking of libraries in C,
plus how to create such libraries.
## Notes
- The examples container here strictly use GCC as the
compiler. For *NIX use the general GNU distribution
of GCC, and for Windows, use MinGW-w64.
- The `-s` flag is used extensively throughout the examples
in this repository, but it must be noted that it is totally
optional and used here only to reduce the output filesize by
removing all symbol table and relocation information.
## Instructions
For different types of linking, I have made:
1. `static`: Static Linking.
2. `dynamic`: Dynamic Linking.
Within each, I have added examples for *NIX and Windows:
1. `nix`: *NIX.
2. `win`: Windows.
Each of the two contains a `Makefile` with a simple
instruction to clean all files built.
Within each of those two, I have created:
1. `library`: The library source code and `Makefile`.
2. `usage`: A simple usage of the same, with the `Makefile`.
The `Makefile`s within those two directories contain a default `build` instruction to compile the code, and
a `clean` instruction to clean all files `built`.
## Information
- The 'link' being referred to in 'symbolic link'
and the one in 'static/dynamic link' are completely
unrelated.
- The source code used for the sample library and the
testing file is container inside `src` in the repository's
root. The source files are symbolically linked into the
desired places, so please ensure you have enabled symbolic
links in Git before cloning.
```bash
git config --global core.symlinks true
```
- In Windows systems, this would also require you to clone via
a console with administrative priviledges, because creating
symbolic links would require them.
- Git won't warn you if you clone without giving
administrative privileges: It will simply create copies
of files instead of symbolcally linking them,
even if you have the global `core.symlinks` set to
`true`. This would
still allow everything to work, but if you need to edit,
for example, `main.c`, the changes won't reflect everywhere
`main.c` is being used.
- To enforce symbolic links while creating the clone,
use
```bash
git clone -c core.symlinks=true https://url/to/repo
```
You don't need to enforce this if you are running
the command-line with administrative privileges.
- If you have Developer Mode enabled in Windows 10,
you won't need to grant administrative privileges for
using symbolic links.
# Made with ❤ by [Param](https://www.paramsid.com).