From: John Gumb <JGumb@Ridgeway-Sys.com>
To: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] "target install/include/pkgconf is not a valid existing directory"
Date: Thu, 23 Aug 2001 04:15:00 -0000 [thread overview]
Message-ID: <00533D13955AD411AF3800A0C9B426391EF089@ThisAddressDoesNotExist> (raw)
Folks,
FWIW, I tried building the command line ecosconfig.exe under cygwin on NT
yesterday (i.e. NOT the MSDEV/graphical tools). Initially, I got the error
messsage
"target install/include/pkgconf is not a valid existing directory"
when doing 'ecosconfig tree'. I tracked this down to generate_build_tree in
build.cxx.
For fun, I guessed paths weren't getting set up correctly so I hacked out
the #ifdef _WIN32 and forced the inclusion of the path fixup code in
$ECOS_REPOSITORY\host\tools\configtool\common\common\build.cxx line 548ish.
All works a treat.
I know this is a gross hack - if I've missed something them pls let me know.
Cheers,
John
$ECOS_REPOSITORY\host\tools\configtool\common\common\build.cxx line 548ish.
// generates the directory structure for the build and install trees
bool generate_build_tree (const CdlConfiguration config, const std::string
build_tree, const std::string install_tree /* = "" */ ) {
/* #ifdef _WIN32 [jag] */
#if 1
// convert backslash directory separators to forward slashes under
Win32
const std::string build_dir = replace_char (build_tree, '\\', '/');
const std::string install_dir = install_tree.empty () ? build_dir +
"/install" : replace_char (install_tree, '\\', '/');
#else
const std::string build_dir = build_tree;
const std::string install_dir = install_tree.empty () ? build_dir +
"/install" : install_tree;
#endif
next reply other threads:[~2001-08-23 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-23 4:15 John Gumb [this message]
2001-08-23 8:22 ` [ECOS] "target install/include/pkgconf is not a valid existing directory " Julian Smart
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=00533D13955AD411AF3800A0C9B426391EF089@ThisAddressDoesNotExist \
--to=jgumb@ridgeway-sys.com \
--cc=ecos-discuss@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).