Become a leader in the IoT community!

New DevHeads get a 320-point leaderboard boost when joining the DevHeads IoT Integration Community. In addition to learning and advising, active community leaders are rewarded with community recognition and free tech stuff. Start your Legendary Collaboration now!

Step 1 of 5

CREATE YOUR PROFILE *Required

OR
Step 2 of 5

WHAT BRINGS YOU TO DEVHEADS? *Choose 1 or more

Collaboration & Work 🤝
Learn & Grow 📚
Contribute Experience & Expertise 🔧
Step 3 of 5

WHAT'S YOUR INTEREST OR EXPERTISE? *Choose 1 or more

Hardware & Design 💡
Embedded Software 💻
Edge Networking
Step 4 of 5

Personalize your profile

Step 5 of 5

Read & agree to our COMMUNITY RULES

  1. We want this server to be a welcoming space! Treat everyone with respect. Absolutely no harassment, witch hunting, sexism, racism, or hate speech will be tolerated.
  2. If you see something against the rules or something that makes you feel unsafe, let staff know by messaging @admin in the "support-tickets" tab in the Live DevChat menu.
  3. No age-restricted, obscene or NSFW content. This includes text, images, or links featuring nudity, sex, hard violence, or other graphically disturbing content.
  4. No spam. This includes DMing fellow members.
  5. You must be over the age of 18 years old to participate in our community.
  6. Our community uses Answer Overflow to index content on the web. By posting in this channel your messages will be indexed on the worldwide web to help others find answers.
  7. You agree to our Terms of Service (https://www.devheads.io/terms-of-service/) and Privacy Policy (https://www.devheads.io/privacy-policy)
By clicking "Finish", you have read and agreed to the our Terms of Service and Privacy Policy.

do you mind handing out a primer on linking vs static compiliing. Especially in the context of GPL?

@ming_58391 while it’s fresh do you mind handing out a primer on linking vs static compiliing. Especially in the context of GPL?

  1. Ming#0000

    For the people that watched the Licences & Vulnerabilities Tech Tips where I talked about linking vs static compiling in the context of GPL…
    When you want to make use of functions in a library within your code you have options:

    So, I have a library, `foo.c` with some functions that I want to use in my application, `bar`
    1. Use the library _statically_ – that means the functions in the library are going to be part of your binary
    – Compile the library
    `gcc -c -o foo.o foo.c`
    – Then make it a static library
    `ar rcs libfoo.a foo.o`
    – Now use it in your code
    `gcc -c bar.c -o bar.o`
    `gcc -o bar bar.o -L. -lfoo`

    You have a single binary that includes both your code and the library’s code.
    This is classed as a _derivative work_ so if the library was LGPL or GPL, then your code must also be GPL

    2. Use the library as a _shared object_
    This means that the library code has been compiled with a `-shared` flag and you end up with a `.so` file – e.g. `libfoo.so`
    In _your_ code you can then link to that library
    `gcc -L. -lfoo -o bar bar.c`

    In this instance, the original library is untouched and your code is just making use of it. As long as the library ls licensed under **LGPL**, then your code can be commercial.

    That is a highly simplified answer – I may do a blog post about it where I can use more space.

    For those of you who didn’t watch the tech tips… Go watch it on the replay!

CONTRIBUTE TO THIS THREAD

Browse other Product Reviews tagged

Leaderboard

RANKED BY XP

All time
  • 1.
    Avatar
    @Nayel115
    1620 XP
  • 2.
    Avatar
    @UcGee
    650 XP
  • 3.
    Avatar
    @melta101
    600 XP
  • 4.
    Avatar
    @lifegochi
    250 XP
  • 5.
    Avatar
    @Youuce
    180 XP
  • 6.
    Avatar
    @hemalchevli
    170 XP