From: Mike_D_Davies@fmo.com
To: sourcenav@sources.redhat.com
Subject: Re: inter project dependencies
Date: Fri, 16 Nov 2001 12:28:00 -0000 [thread overview]
Message-ID: <OF3D98FF7B.F728E1AB-ON80256B17.0048C0FC@na.fmo.com> (raw)
Jordan <jordan.howarth@cmis.csiro.au>@sources.redhat.com on 03/12/2001
11:30:58
Sent by: sourcenav-owner@sources.redhat.com
To: Ian Roxborough <irox@redhat.com>
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
next reply other threads:[~2001-12-03 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 12:28 Mike_D_Davies [this message]
2001-11-21 0:56 ` Mark Thornber
2001-11-21 13:33 ` Jordan
-- strict thread matches above, loose matches on Subject: below --
2001-11-14 4:22 Jordan
2001-11-14 6:17 ` Ian Roxborough
2001-11-14 10:50 ` Jordan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF3D98FF7B.F728E1AB-ON80256B17.0048C0FC@na.fmo.com \
--to=mike_d_davies@fmo.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).