This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: Build tree paths
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