From: "Peter Münster" <pmlists@free.fr>
Subject: Re: compiling project files
Date: Mon, 14 Aug 2006 22:44:37 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0608142242530.9306@gaston.pm> (raw)
In-Reply-To: <221cc89e0608122039vb9709e3oc232ffd2f00f011c@mail.gmail.com>
On Sat, 12 Aug 2006, Derek Schmidt wrote:
> The .tuo file for the _product_ file shows the files being loaded.
> Compiling the _project_ file yields no .tuo. My product file does
> indeed look like what you wrote.
Hello Derek,
it's not intended to compile the project file. It should contain only
common setups for all products.
Only components and products should be compiled.
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2006-08-14 20:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:52 Derek Schmidt
2006-08-09 16:26 ` Tobias Burnus
2006-08-09 16:27 ` Aditya Mahajan
2006-08-13 3:39 ` Derek Schmidt
2006-08-13 15:46 ` Mojca Miklavec
2006-08-14 20:44 ` Peter Münster [this message]
2006-08-15 20:16 ` Boris Tschirschwitz
2006-08-15 20:29 ` Aditya Mahajan
2006-08-16 15:58 ` Mojca Miklavec
2006-08-16 16:07 ` Taco Hoekwater
2006-08-16 22:52 ` Hans Hagen
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=Pine.LNX.4.58.0608142242530.9306@gaston.pm \
--to=pmlists@free.fr \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).