From: Robin Farine <robin.farine@terminus.org>
To: git@vger.kernel.org
Subject: Re: [ANNOUNCE qgit-0.95]
Date: Sun, 25 Sep 2005 20:46:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20050925T222758-893@post.gmane.org> (raw)
In-Reply-To: 200509252056.04403.Josef.Weidendorfer@gmx.de
Josef Weidendorfer <Josef.Weidendorfer <at> gmx.de> writes:
> On Sunday 25 September 2005 09:07, Marco Costalba wrote:
> > >> src/rangeselectbase.h QSettings: error creating /.qt
> > >>QSettings: error creating /.qt
> > ...
> > QSettings are there from day one :-<
> > I am not able to let them disappear.....very bad. In any case should be
> > harmless.
>
> These errors seam to appear because scons does NOT pass through the $HOME
> environment variable to subprocesses. "moc", which is producing these
> errors, obviously wants to access some config options in $HOME/.qt/.
>
> Somebody knows how to change this?
With SCons, key-value pairs that are meant to appear in process
environment need to be added to the env['ENV'] mapping. In this
case:
env = Environment(...)
env['ENV']['HOME'] = os.environ['HOME']
Environment() creates an SCons build environment which is unrelated
to subprocess environments (even though the same word is used :)).
As a special case, SCons handles the mapping assigned to env['ENV']
as process environment for subprocesses.
Hope this helps,
Robin
next prev parent reply other threads:[~2005-09-25 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 7:07 [ANNOUNCE qgit-0.95] Marco Costalba
2005-09-25 18:56 ` Josef Weidendorfer
2005-09-25 20:46 ` Robin Farine [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-25 21:57 Marco Costalba
2005-09-25 20:37 Marco Costalba
2005-09-25 5:52 Marco Costalba
2005-09-25 19:19 ` Josef Weidendorfer
2005-09-24 16:06 Marco Costalba
2005-09-24 18:16 ` Petr Baudis
2005-09-25 6:32 ` Alan Chandler
2005-09-25 6:47 ` Alan Chandler
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=loom.20050925T222758-893@post.gmane.org \
--to=robin.farine@terminus.org \
--cc=git@vger.kernel.org \
/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