Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@AlgoRythm oh shut up lol
-
@AlgoRythm bad person lol
-
@sariel so what if cmake isn't finding them ? :P
this is why i hate cmake
the old build system would have found them if they were in the pkg-config directories !! -
@AvatarOfKaine if you run checkinstall it directly creates a .deb file and installs it with dpkg.
You often only need to provide a version number and nothing else it is like magic -
@AvatarOfKaine you likely need to include them directly in your code or find a way to install them onto the os.
-
@sariel it's a 3rd party package im trying to compile with its own explicit instructions for my distro and the fucker used cmake and doesn't just die if one or more binaries don't compile for "missing" deps
-
@AvatarOfKaine yuck, my condolences.
-
@sariel but whyyyyyyyy ?
I crave 'make'
'oh shit your build died at this location missing fucking reference or definition chain referned by these 200 fucking source files ! fix it or NO' LOL -
@sariel what kind of build utility, designed by sadists in the first place would HALF BUILD !!!
-
@AvatarOfKaine there's definitely a time and place to use cmake. Building c native libs for other languages like Ruby.
But that's about it.
is there a fucking utility that will flat out list all installed libraries on a linux system and if cmake and/or pkg-config can find them ???
question