I can’t include an .so file in my c++ project
I am trying to include libcurl in my large c++ project, which I am building on Ubuntu 24.04 using Visual Studio Code, CMake, and gcc.
I can’t include an .so file in my c++ project
I am trying to include libcurl in my large c++ project, which I am building on Ubuntu 24.04 using Visual Studio Code, CMake, and gcc.
I can’t include an .so file in my c++ project
I am trying to include libcurl in my large c++ project, which I am building on Ubuntu 24.04 using Visual Studio Code, CMake, and gcc.
Why used printf the same variable addr twice result in different print values?
Environnment:
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?
Functionally achieve –ffunction-sections from assembly
I’m linking against a static library that I don’t have the original source code to, and it’s absolutely critical that I produce the smallest binary. Although unused .text
sections from this library get stripped, if (e.g.) there’s a .o
containing even a single function that my code uses, then the entire .text
section of that object gets linked into the final executable. Is there a way to link more selectively?