[Contents][Index][Top][Prev][Next]

2.2   Advice Concerning the Use of config.h and configAll.h

There are times when VxWorks configuration must be fine-tuned beyond the capabilities of the configuration tool described in the Tornado User's Guide: Projects. In these cases, you should edit configuration header files manually to modify constants and macros.

The config.h file sets values for constants that the build uses to determine the contents of a VxWorks image. The tricky part of editing config.h is determining where you want to insert the #define or #undef statement. This is because all config.h files contain a #include "configAll.h" statement.


*
WARNING: You should avoid modifying the configAll.h file.

Within the configAll.h file, there are #ifdef blocks that depend on the value of a symbolic constant whose value you might want to modify. You should insert any change to config.h that modifies such constants before the inclusion of configAll.h. However, configAll.h sometimes undefines a symbolic constant that you might want to define. In such cases, you should put your #define statement after the inclusion of configAll.h. As a consequence, before you modify a value in a BSP's config.h file, you must first check the configAll.h file for dependencies on the constant you want to modify.

If you modify the config.h file, be sure to refer to the Tornado User's Guide: Projects for advice on how to coordinate these changes with ones you make using the configuration tool.

[Contents][Index][Top][Prev][Next]