In a command window, change to the top-level directory of the EDK II source.\r
\r
To test your tool chain setup and to build the supplied tools, execute:\r
- c:\MyWork\edkii\> edksetup ForceBuild\r
+ c:\MyWork\edkii\> edksetup ForceRebuild\r
\r
(The edksetup script is referred to as the setup command throughout the \r
rest of this document.)\r
edksetup script. Example: export TOOL_CHAIN=gcc\r
\r
To test your tool chain setup and to build the supplied tools, execute:\r
- c:\MyWork\edkii\> edksetup ForceBuild\r
+ c:\MyWork\edkii\> edksetup ForceRebuild\r
\r
On Linux systems, you must source the edksetup.sh file to load the correct\r
settings into your shell.\r
\r
. edksetup.sh # Note the dot.\r
\r
+If you have recently updated your code from subversion, the tools will need to\r
+be rebuilt if there were any code changes made to them. You can request that\r
+the tools get rebuilt by typing:\r
+\r
+ . edksetup.sh Rebuild # Unix-like systems\r
+ edksetup.bat Rebuild # Windows\r
+\r
The edksetup script is referred to as the setup command throughout the \r
rest of this document.\r
NOTE: You should run the setup command at the start of every session.\r
\r
Any changes to the tool source code or XML Schema documents require that\r
you execute the following:\r
- c:\MyWork\edkii\> edksetup ForceBuild\r
+ c:\MyWork\edkii\> edksetup ForceRebuild\r
\r
You must set the WORKSPACE environment variable, or run the edksetup\r
script (without any arguments), any time you want to build.\r