Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Sep 7 08:13:10 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m87FDACt007707 for ; Sun, 7 Sep 2008 08:13:10 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m87FBtH1012162 for ; Sun, 7 Sep 2008 08:11:55 -0700 Message-Id: <200809071511.m87FBtH1012162@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: separate compilation Date: Sun, 07 Sep 2008 08:11:55 -0700 From: Bill Cheng Someone wrote: > For separate compilation how many module we need to make. I have 3 module, > common, client and server. Do I need to break client and server into > separate modules for ADDR, FILESIZE and GET request handler modules? For each executable, you need at least 2 modules. So, it's perfectly fine to link "common.o" and "client.o" to create "client" and to link "common.o" and "server.o" to create "server". -- Bill Cheng // bill.cheng@usc.edu