From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22562 invoked by alias); 3 Dec 2001 14:58:16 -0000 Mailing-List: contact sourcenav-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sourcenav-owner@sources.redhat.com Received: (qmail 22539 invoked from network); 3 Dec 2001 14:58:15 -0000 Message-ID: <3C0B92F9.9010202@iee.org> Date: Wed, 21 Nov 2001 00:56:00 -0000 From: Mark Thornber Organization: Enchanted Systems Limited User-Agent: Mozilla/5.0 (Windows; U; Win98; en-GB; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-gb MIME-Version: 1.0 To: jordan.howarth@cmis.csiro.au CC: sourcenav@sources.redhat.com Subject: Re: inter project dependencies References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2001-q4/txt/msg00032.txt.bz2 Jordan, Adding projects to an existing SN project just creates a bigger, monolithic, project - there is no concept of sub-projects as in SNiFF+ Things work - but the downside is the length of time taken to reparse etc. HTH -- MarkT Mike_D_Davies@fmo.com wrote: > > > > > > > Jordan @sources.redhat.com on 03/12/2001 > 11:30:58 > > Sent by: sourcenav-owner@sources.redhat.com > > > To: Ian Roxborough > cc: sourcenav@sources.redhat.com > Subject: Re: inter project dependencies > > > > Alas I fear I have spent too long on the dark side :( In MSVC, the > term for the scope of an entire software build is a workspace which > consists of individual projects. So some projects can be libraries and > one can be the responsible for linking these in order to produce the > final executable (apologies for lessons in egg sucking). Mapping this > to SN and you have one project specifying the scope for multiple > targets, no? To me, this reflects a conventional makefile. > > Assuming that this is correct, let me rephrase my earlier > question. How do I make one target depend on another in SN? > > > > > > Hi, > > If you start the project editor (Files/Project Editor in the Symbols > window) then there is a button for adding a project (*.proj file). I > haven't tried it but you could try starting a completely new project (maybe > called workspace ?) and then adding the individual projects that you want > to be part of your workspace to that. Then the top level build should > build all your parts and the component projects could still be built from > their individual projects ? > > You may need to change the build command for the top level project - as I > said I haven't tried this so it may not work. > > > Let us know how you get on ;-) > > > Mike Davies > > > >