Autotools

Back to Remote Builds for a Moment

As we wrap up this chapter, you'll notice that we've come full circle. We started out covering some preliminary information before we discussed how to add remote builds to Jupiter. Now we'll return to this topic for a moment, because I haven't yet covered how to get the C preprocessor to properly locate a generated config.h file.

Since this file is generated from a template, it will be at the same relative position in the build directory structure as its counterpart template file, config.h.in, is in the source directory structure. The template is located in the top-level source directory (unless you chose to put it elsewhere), so the generated file will be in the top-level build directory. Well, that's easy enough—it's ...