object-files

来源： https://stackoverflow.com/questions/64073080/convert-binutils-size-output-from-sysv-format-size-format-sysv-my-execut

来源： https://stackoverflow.com/questions/64073080/convert-binutils-size-output-from-sysv-format-size-format-sysv-my-execut

来源： https://stackoverflow.com/questions/64073080/convert-binutils-size-output-from-sysv-format-size-format-sysv-my-execut

问题 I have a small (<300 lines) C++ file in a C++ CLI project in Visual Studio 2010. I have crafted some macros which do different things depending on the Debug/Release configurations. I would like to be able to look at the resulting .obj files (when I compile in Debug and Release) and be able to compare the two. The hard part is that files are binary and I do not understand their format. I am sure there are other ways to ensure that the macro is not destructive - e.g. try it out at runtime in

问题 how to see what .o files constitute .so file? Means how to notice what are the object files are used to build the .so file from the .so file (If I have only the .so file) 回答1: You can't know , given just a shared library, what object files were compiled into it. If you're lucky, you may be able to make a reasonable guess. A shared library is made, by the linker, from object files and possibly other shared libraries, but it does not contain the object files or shared libraries from which it

问题 how to see what .o files constitute .so file? Means how to notice what are the object files are used to build the .so file from the .so file (If I have only the .so file) 回答1: You can't know , given just a shared library, what object files were compiled into it. If you're lucky, you may be able to make a reasonable guess. A shared library is made, by the linker, from object files and possibly other shared libraries, but it does not contain the object files or shared libraries from which it

问题 I know .OBJ is the result of compiling a unit of compilation and .LIB is a static library that can be created from several .OBJ, but this difference seems to be only in the number of units of compilation. Is there any other difference? Is it the same or different file format? I have come to this question when wondering if the same static variable defined in two (or more) .LIBs is merged or not during linking into the final executable. For .OBJs the variables are merged. But is it the same in

问题 I followed the ways mentioned in Link object file to my project Eclipse CDR My main function is in cpp code and from that I wish to call a c-function. So for that I created the object file (.o) from the c-code using gcc -c -fpic mycode.c This gave me a ".o" file which I wanted to link to the cpp code. I created a header file with reference to http://www.parashift.com/c++-faq/include-c-hdrs-nonsystem.html Header file was declared as an extern in my cpp code. The header file contains to

问题 This is really a linker / object-file question, but tagging with assembly since compilers never do this. (Although maybe they could!) Consider this function, where I want to handle one special case with a block of code that's in the same I-cache line as the function entry-point. To avoid jumping over it in the usual fast-path, is it safe (wrt. linking / shared libraries / other tools I haven't thought of) to put the code for it ahead of the function's global symbol? I know this is silly /

问题 I'm working on a project from school, and we were given a .o and a corresponding .h file. We need to use several functions from the .o file in our .c program. Just placing it in the same directory doesn't work. I tried to look for something like this in the project properties, but no good. I keep getting ../code_files/Search.c:116: undefined reference to 'reportError' I'm using Eclipse (Juno) CDT, gcc MinGW under Windows 7 I know it's possible to include .a files, but I couldn't find any