Module 3-1: Building with DIRS and SOURCES

Transcription

1 Module 3-1: Building with DIRS and SOURCES Contents Overview 1 Lab 3-1: Building with DIRS and SOURCES 9 Review 10

2 Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

3 Module 3-1: Building with DIRS and SOURCES iii Instructor Notes Day 3 Build System Under the Hood This day focuses on the details of each stage of the build process covering what programs or script files are used in each stage. The details will include the input data set, the programs/ scripts that implement the functionality of the build stage and the resulting output files. This will include best practices for providing/using third party modules and components in the build. The lecture and labs for this day build up a custom public folder that participates in the OS build exactly the same way that the Microsoft provided code does. Starting with a simple DIRS and SOURCES build and ending up with a sysgen filtered DLL module with multiple selectable components and private source code. Learning points Understand the build stages including the inputs to each stage, the programs or script files used in each stage and the outputs of each Location and organization of the various code files in the build tree Understand differences between components and modules and how to select them in a build Understanding PBPXML files and their uses in the build Module 3-1 Presentation: 45 minutes Lab: 45 minutes Required materials Preparation tasks Build.exe along with DIRS and SOURCES files have been the underlying build engine for Windows CE since it s very beginning. However since the introduction of Platform Builder many users have become disconnected from the underlying mechanics of the build. This module covers the details of how to use DIRS and SOURCES files including some of the new SOURCES file settings available in V5.0. In this module, students will learn: Build.exe is the central build engine that manages compiling source code in to libraries, DLLs, and EXEs DIRS files are conceptually a workspace for individual SOURCES files SOURCES files are conceptually a project that is used to define SOURCES.CMN provides settings common to a set of SOURCES projects SOURCES files are just an include file to a larger MAKEFILE Build.exe adds DIRS processing and automatic dependency generation to MAKEFILES To teach this module, you need Microsoft PowerPoint file Module 3-1.ppt. To prepare for this module: Read all the material for this module. Complete the lab.

4 iv Module 3-1: Building with DIRS and SOURCES

5 Module 3-1: Building with DIRS and SOURCES 1 Overview Introduction Objectives In this module, you will learn: Build.exe is the central build engine that manages compiling source code in to libraries, DLLs, and EXEs DIRS files are conceptually a workspace for individual SOURCES files SOURCES files are conceptually a project that is used to define SOURCES.CMN provides settings common to a set of SOURCES projects SOURCES files are just an include file to a larger MAKEFILE Build.exe adds DIRS processing and automatic dependency generation to MAKEFILES

6 2 Module 3-1: Building with DIRS and SOURCES Build.exe Build.exe is used in the DDK for desktop windows and also used internally at Microsoft to build the OS

7 Module 3-1: Building with DIRS and SOURCES 3 Build.exe You can get this information from a build command window by typing: Build /?

8 4 Module 3-1: Building with DIRS and SOURCES DIRS Files

9 Module 3-1: Building with DIRS and SOURCES 5 SOURCES Buildexe uses nmake to build source code files. The folder with a SOURCES file MUST also have a makefile that includes makefile.def from %_MAKEENVROOT%. MAKEFILE.DEF includes the local SOURCES file to provide the list of source files to build along with settings for the build. MAKEFIL.DEF contains a significant amount of standard functionality to keep the SOURCES files generally simple.

10 6 Module 3-1: Building with DIRS and SOURCES SOURCES The SOURCES file is just an include in a Makefile so it as the same syntax. The primary purpose is to set various Macro variables for the target

11 Module 3-1: Building with DIRS and SOURCES 7 SOURCES The primary difference between TARGETLIBS and SOURCELIBS is where they are placed (if at all) on the command line to the linker.

12 8 Module 3-1: Building with DIRS and SOURCES SOURCES These commands can be any valid command line command but are typically a call to a BAT file to do whatever work is needed.

13 Module 3-1: Building with DIRS and SOURCES 9 SOURCES and the IDE These variables are used only in the IDE and are simply helpful user interface information. They are otherwise ignored by the build system.

14 10 Module 3-1: Building with DIRS and SOURCES MAKEFILE.DEF If you really wish to understand the build system in Windows CE you should spend the time to read and understand each part of this makefile. It is the central core of the build

15 Module 3-1: Building with DIRS and SOURCES 11 SOURCES.CMN Typically your SOURCESCMN will set values for multiple SOURCES projects. Windows CE 5.0 stopped using srcgen to establish these variables automatically.

16 12 Module 3-1: Building with DIRS and SOURCES Lab 3-1: Building with DIRS and SOURCES Introduction This lab sets up the GeneriCo public folder from the GeneriCoBase template files. This public folder serves as the basis for the rest of the labs for this day. A static library is created, a DLL is created that uses the static lib and an application is created that uses the DLLs import library. This sets up how SOURCES projects use the output of one as the input for another and how a SOURCES file can generate each type of output.

17 Module 3-1: Building with DIRS and SOURCES 13 Review 1. What is the difference between TARGETLIBS and SOURCELIBS The primary difference between TARGETLIBS and SOURCELIBS is where they are placed (if at all) on the command line to the linker 2. What has changed for V5.0 SOURCES files from previous versions? The build no longer has/uses the srcgen tool to automatically generate _OMEINCPATH, and _ISVINCPATH 3. What is the primary build engine for Windows CE? Build.exe