14
Kyu96
68d

FUCCCCKCKCKKC FUCK FUCK FUCK FUCKING CUNTFUCK BULLSHTI FUCKK!
I SWEAR TO GOD LINKING LIBRARIES IN C++ IS THE WORST FUCKIGN THING ON THE ENTIRE FUCKIGN PLANET.
sfjipomndgsm8h rteügj8jq9rtg

Comments
  • 0
    Just type -llibname -L path as flags though?

    You can omit the -L path if it is in your libs folder.
  • 2
    Agreed, but you get used to it and it becomes okay
  • 0
    @BigBoo Its not that easy.
  • 0
    @Kyu96 Why not? What are you trying to link?
  • 0
    @BigBoo Paho mqtt. I got it linked but I have a shitload of other problems
  • 0
    @Kyu96 Welp, can't help you with that. But if you have problems with linking libraries I can recommend trying to write your own simple library, compile it as a library and then use it in some other code to get a feel of the process.
  • 0
    Vs code? Took me 4 hours to wrap my head around linking/libs with it..

    g++ main.cxx -o main.o -L /path/to/lib

    This was so much easier..
  • 0
    how is this difficult. You need to try to build a dev environment for some legacy java backend project. Have fun with all the dependencies, they all want a specific version and all the errors don't tell you what version is that.
  • 0
    @Kyu96 I prefer writing build scripts in a meta system like CMake, makes it much easier. It can also search for libraries by name (if they were installed in a certain way) and pull them into your build.
  • 0
    @RememberMe I am doing that. The issue is actually the fuckibg library that is annoying not cmake
  • 1
    Fuck dude, it took me installing an isolated dev environment in /opt on my Linux machine to understand linking and includes.
Your Job Suck?
Get a Better Job
Add Comment