Fantastic. it's now working. I need to pull in MSYS's make.exe, tee.exe,
hostname.exe, date.exe, dirname.exe, and basename.exe to make my
configure and build process work.=20
One flaw I had been having was using cygwin's ln -s to create a symlink,
and well, DOS couldn't see it. I switched to mkdir and now everything
seems to be working fine.=20
Ooh, one more thing. How do I take an MSYS POSIX path and add it to the
windows PATH variable? I generate some bash scripts to run my
development tools (the ones that I've built as part of this build
process) and one of the things they need to do is augment the PATH (on
Unix they augment LD_LIBRARY_PATH).=20
> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd@...]
> Sent: Thursday, December 20, 2001 10:42 AM
> To: Andrew Begel
> Cc: MM List
> Subject: Re: [Mingw-msys] Re: configure problems with MSYS 1.02
> Andrew Begel wrote:
> > On Thursday, December 20, 2001, at 05:09 AM, Earnie Boyd wrote:
> > > Hmm..., I think I see what you're driving at, you=20
> generated a Makefile
> > > using MSYS and tried using Cygwin to execute the make=20
> command. That
> > > isn't sane, and is like generating a Makefile on one=20
> system and taking
> > > it to a different system to be used to build the package.=20
> It ain't
> > > going to fly, no one should expect that it would. That is also
> > > analogous to building a model airplane with the parts=20
> from one style of
> > > airplane and the instructions from another.
> > >
> > Yeah, now you've got it. So I used configure under an MSYS bash to
> > generate my Makefile from my Makefile.in, and now what? All=20
> the paths
> > that configure figured out where MSYS-style paths. Now, if=20
> there's no
> > gmake that understands MSYS paths, I'm kinda stuck, no? All=20
> these great
> > paths and nowhere to use them...
> No, you're not stuck. The POSIX paths get translated to native win32
> paths under MSYS. That's the point of MSYS. That's why it exists.
> > There are two categories of translations that I'll need=20
> then, if I try
> > to use gmake from MinGW or gmake from cygwin (more likely).=20
> POINT: You can't mix Cygwin and MSYS. There is a gmake=20
> distributed with
> MSYS if you need that one use that _NOT_ the Cygwin make.
> > I need to
> > translate MSYS paths to DOS paths (if I use DOS tools, such as MinGW
> > gcc.exe or a native XEmacs -batch to run some Lisp code) and also
> > translate MSYS paths to cygwin paths (for unix-like tools,=20
> such as "sed"
> > and "awk" and other nice utilities I use in my build process).
> Forget using Cygwin with MSYS, not possible. The point of MSYS is to
> translate the paths on the arguments so that POSIXised paths get
> translated to Win32 style paths without you needing to think=20
> about it.=20
> As for the nice unix utilities, what's missing from MSYS that you need
> for building native MinGW applications?
> > Without the translation, or the ability to run Makefiles in=20
> MSYS using
> > an MSYS gmake, I don't see how MSYS could be useful at=20
> all.... Please
> > correct my line of reasoning here, if I'm just not seeing=20
> the right big
> > picture.
> I thought that you said you were able to use MSYS to build your
> application. What exactly are you having a problem with? I'm lost in
> your confusion. All that you should need do is
> make (if you want the MinGW version of make) or `gmake=20
> MAKE=3Dgmake' (for
> the MSYS version of make).
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com