From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15865 invoked by alias); 3 Dec 2001 23:07:22 -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 15829 invoked from network); 3 Dec 2001 23:07:18 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 21 Nov 2001 13:33:00 -0000 From: Jordan To: Mark Thornber Cc: sourcenav@sources.redhat.com Subject: Re: inter project dependencies In-Reply-To: <3C0B92F9.9010202@iee.org> References: <3C0B92F9.9010202@iee.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <15372.984.644508.991297@pride.nsw.cmis.CSIRO.AU> X-SW-Source: 2001-q4/txt/msg00033.txt.bz2 WRT Mike Davies suggestion, Mark's observation was my own - obviously motivated by the same things that caused "duplicate project" to be included in SNav interface. I think my revised request idenitifies the issue in sufficiently unambiguous terms, free of my confusion over differences in terminology between MSVC and SNav. Mark> Jordan, Adding projects to an existing SN project just Mark> creates a bigger, monolithic, project - there is no concept Mark> of sub-projects as in SNiFF+ Mark> Things work - but the downside is the length of time taken Mark> to reparse etc. Mark> HTH -- MarkT Mark> 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 >> >> >> >> -- Jordan Howarth mailto:jordan.howarth@cmis.csiro.au CSIRO p: (07) 3375 9632, (07) 3826 7314 Mathematical and Information Sciences f: (07) 3826 7304 -=| For every truth there are a thousand lies |=-