From: Gary Thomas <gary@mlbassoc.com>
To: John Dallaway <jld@ecoscentric.com>
Cc: "Timothy M. Schaeffer" <tschaeffer@dramail.com>,
ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: Build tree paths
Date: Mon, 11 Feb 2008 12:07:00 -0000 [thread overview]
Message-ID: <47B03A87.8020201@mlbassoc.com> (raw)
In-Reply-To: <47B0111A.30209@ecoscentric.com>
John Dallaway wrote:
> Hi Tim
>
> Timothy M. Schaeffer wrote:
>
>> Say I'm generating a build tree with x.ecc. When I generate the build
>> tree in config tool, I get 3 directories: x_install, x_mlt, x_build.
>> But if I do
>>
>> $ ecosconfig --config=x.ecc
>>
>> I get everything that would have been in the x_build and x_install
>> directories in the current directory.
>>
>> $ ecosconfig --config=x.ecc --prefix=x_install
>>
>> can move the install stuff, but the build stuff still gets dumped into
>> the current directory. This makes it difficult to move between using
>> configtool and ecosconfig.
>>
>> - Why doesn't ecosconfig do what configtool does?
>>
>> - How can I make it do what configtool does?
>
> ecosconfig assumes the the current working directory is the base of the
> build tree. Try the following:
>
> $ cd /path/to/x_build
> $ ecosconfig --config=/path/to/x.ecc --prefix=/path/to/x_install
But (and I've asked this myself for many years now) are they different
in the first place?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-02-11 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 20:56 [ECOS] " Timothy M. Schaeffer
2008-02-11 9:11 ` [ECOS] " John Dallaway
2008-02-11 12:07 ` Gary Thomas [this message]
2008-02-11 12:41 ` John Dallaway
2008-02-13 23:32 ` Timothy M. Schaeffer
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=47B03A87.8020201@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jld@ecoscentric.com \
--cc=tschaeffer@dramail.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).