Re: Wine's path VS host path

2002-02-15 Thread David Elliott
On 2002.02.14 22:08 David D. Hagood wrote: > [EMAIL PROTECTED] wrote: > >> Pity you couldn't use some other environment variable. The entire unix > Yes, but make must also be able to find the tools, hence they are in the > path (I am using Linux's binfmt_misc with the appropriate settings so >

Re: Wine's path VS host path

2002-02-15 Thread David D. Hagood
Andreas Mohr wrote: > On Thu, Feb 14, 2002 at 06:17:56PM -0600, David D. Hagood wrote: > > My newly submitted patch "implement "App Paths" support" might just be > what you need... > (disclaimer: I did *not* implement it for you ! :-) > > I would never be so foolish as to expect someone to im

Re: Wine's path VS host path

2002-02-15 Thread Andreas Mohr
On Thu, Feb 14, 2002 at 06:17:56PM -0600, David D. Hagood wrote: > Due to circumstances beyond my control, I have an embedded system that I > am developing that uses Windows based compilers. Unfortunately, WinNT > bluescreens too much for me to be able to work, so I have ported the > project to

Re: Wine's path VS host path

2002-02-15 Thread lawson_whitney
On Fri, 15 Feb 2002, Michael Cardenas wrote: > actually, I don't see a path specified in my wine config file, are you sure > that's how it gets the unix path? [wine] "Path" = > > and if it is stored in the config file, you could just use a pretty simple > sed or perl script to insert it into th

Re: Wine's path VS host path

2002-02-15 Thread David D. Hagood
The problems with adding the code directly to the Wine config path are: 1) We package the tools along with the project - that way, if the tools are updated for a giving build, they will always be available with that build. I've done too much code archeology where I couldn't build a release bec

Re: Wine's path VS host path

2002-02-15 Thread Michael Cardenas
ROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, February 14, 2002 6:25 PM Subject: Re: Wine's path VS host path > On Thu, 14 Feb 2002, David D. Hagood wrote: > > > Due to circumstances beyond my control, I have an embedded system that I > &

Re: Wine's path VS host path

2002-02-14 Thread lawson_whitney
On Thu, 14 Feb 2002, David D. Hagood wrote: > The project is a rather large one, comprised of over 9000 files in many > different directories. Having the tools always in CWD isn't an option. > Well, maybe I am stupid, but I don't see why you can't just install the tools somewhere, and add the win

Re: Wine's path VS host path

2002-02-14 Thread David D. Hagood
[EMAIL PROTECTED] wrote: > Pity you couldn't use some other environment variable. The entire unix Yes, but make must also be able to find the tools, hence they are in the path (I am using Linux's binfmt_misc with the appropriate settings so that the programs are directly executable). > compi

Re: Wine's path VS host path

2002-02-14 Thread lawson_whitney
On Thu, 14 Feb 2002, David D. Hagood wrote: > Due to circumstances beyond my control, I have an embedded system that I > am developing that uses Windows based compilers. Unfortunately, WinNT > bluescreens too much for me to be able to work, so I have ported the > project to using Gnu Make, with t

Wine's path VS host path

2002-02-14 Thread David D. Hagood
Due to circumstances beyond my control, I have an embedded system that I am developing that uses Windows based compilers. Unfortunately, WinNT bluescreens too much for me to be able to work, so I have ported the project to using Gnu Make, with the compilers being executed via Wine. The problem