header-files

I am getting a really odd error from GCC 4.8.1 with inline functions. I have two near-identical inline functions defined in header files ( debug.h and error.h ) in src/include/ , with the only difference being what they print - one prefixes DEBUG: to the message, and the other %s: error: %s (program name, error message). When defining the functions both inline, and compiling a debug build (so it sets the macro DEBUG=1 ), I get lots of undefined reference errors: src/main_debug.o gcc -osrc/main_debug.o src/main.c -c -Wall -Wextra -Wpedantic -std=gnu11 -march=native -Og -g -DCC="\"gcc\""

I'm successfully calling my Swift classes from Objective C (for target 'MyApp') via the import statement: #import "MyApp-Swift.h" I've now created a new target called "MyAppLite" When I compile the new target, I get errors because "MyApp-Swift.h" is required by the code, but the compiler is creating "MyAppLite-Swift.h" So, I need to create a conditional Swift/ObjC header #import for the target I'm compiling against. How can this be done, or is there a better way? C0D3LIC1OU5 It is also possible to set the Product Module Name setting in Build Settings to be the same across your modules (I set

I recently posted a question asking for what actions would constitute the Zen of C++ . I received excellent answers, but I could not understand one recommendation: Make header files self-sufficient How do you ensure your header files are self-sufficient ? Any other advice or best-practice related to the design and implementation of header files in C/C++ will be welcome. Edit: I found this question which addresses the "Best Practices" part of mine. shoosh A self sufficient header file is one that doesn't depend on the context of where it is included to work correctly. If you make sure you

I have a project (a library) that is subdivided into a few directories with code in them. I'd like to to have g++ search for header files in the project's root directory, so I can avoid different include paths for same header files across multiple source files. Mainly, the root/ directory has sub-directories A/ , B/ and C/ , all of which have .hpp and .cpp files inside. If some source file in A wanted to include file.hpp , which was in B, it would have to do it like this: #include "../B/file.hpp" . Same for another source file that was in C. But, if A itself had sub-directories with files that

I've perused the possible duplicates, however none of the answers there are sinking in. tl;dr: How are source and header files related in C ? Do projects sort out declaration/definition dependencies implicitly at build time? I'm trying to understand how the compiler understands the relationship between .c and .h files. Given these files: header.h : int returnSeven(void); source.c : int returnSeven(void){ return 7; } main.c : #include <stdio.h> #include <stdlib.h> #include "header.h" int main(void){ printf("%d", returnSeven()); return 0; } Will this mess compile? I'm currently doing my work in