can't find winedbg

[Christopher Harvey]

I just built wine out of git.
Ran this:
wine-git $ find . -name winedbg
./programs/winedbg

notice there is no winedbg program. The output there is a folder only.
Where is the winedbg program within the git tree?

[Mike Kaplinskiy]

On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
 wrote:
> I just built wine out of git.
> Ran this:
> wine-git $ find . -name winedbg
> ./programs/winedbg
>
> notice there is no winedbg program. The output there is a folder only.
> Where is the winedbg program within the git tree?

I'm pretty sure it's inside that folder and it itself is a wine
executable, so you would run it like:

./wine ./programs/winedbg/winedbg.exe.so

Mike.

[Ben Klein]

2009/5/5 Mike Kaplinskiy :
> On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
>  wrote:
> > I just built wine out of git.
> > Ran this:
> > wine-git $ find . -name winedbg
> > ./programs/winedbg
> >
> > notice there is no winedbg program. The output there is a folder only.
> > Where is the winedbg program within the git tree?
>
> I'm pretty sure it's inside that folder and it itself is a wine
> executable, so you would run it like:
>
> ./wine ./programs/winedbg/winedbg.exe.so

Indeed. This will yield the results you want:
$ find . -type f -name 'winedbg*'

[Christopher Harvey]

Ben Klein wrote:
> 2009/5/5 Mike Kaplinskiy :
> > On Mon, May 4, 2009 at 9:27 PM, Christopher Harvey
> >  wrote:
> > > I just built wine out of git.
> > > Ran this:
> > > wine-git $ find . -name winedbg
> > > ./programs/winedbg
> > >
> > > notice there is no winedbg program. The output there is a folder only.
> > > Where is the winedbg program within the git tree?
> >
> > I'm pretty sure it's inside that folder and it itself is a wine
> > executable, so you would run it like:
> >
> > ./wine ./programs/winedbg/winedbg.exe.so
>
> Indeed. This will yield the results you want:
> $ find . -type f -name 'winedbg*'

Got it going. thanks. I did a bit of wine dev a few years back. I don't
remember it being like this. Maybe this should be noted on the
developers cheat sheet and manual, if it isn't already.

[Vitaliy Margolen]

Mike Kaplinskiy wrote:
> executable, so you would run it like:
>
> ./wine ./programs/winedbg/winedbg.exe.so

'./wine winedbg' will do the same.

Vitaliy.

[Ben Klein]

2009/5/5 Vitaliy Margolen :
> Mike Kaplinskiy wrote:
> > executable, so you would run it like:
> >
> > ./wine ./programs/winedbg/winedbg.exe.so
>
> './wine winedbg' will do the same.

Will that look-up in ./programs/winedbg before looking in $PREFIX/lib/wine/?

[Vitaliy Margolen]

Ben Klein wrote:
> 2009/5/5 Vitaliy Margolen :
> > Mike Kaplinskiy wrote:
> > > executable, so you would run it like:
> > >
> > > ./wine ./programs/winedbg/winedbg.exe.so
> >
> > './wine winedbg' will do the same.
>
> Will that look-up in ./programs/winedbg before looking in $PREFIX/lib/wine/?

Should. I don't have Wine installed (and never had) but winedbg, notepad,
winecfg & all other programs work just fine.

Vitaliy.

[Ken Sharp]

Vitaliy Margolen wrote:
> Ben Klein wrote:
> > 2009/5/5 Vitaliy Margolen :
> > > Mike Kaplinskiy wrote:
> > > > executable, so you would run it like:
> > > >
> > > > ./wine ./programs/winedbg/winedbg.exe.so
> > >
> > > './wine winedbg' will do the same.
> >
> > Will that look-up in ./programs/winedbg before looking in $PREFIX/lib/wine/?
>
> Should. I don't have Wine installed (and never had) but winedbg, notepad,
> winecfg & all other programs work just fine.

It seems to.

./wine is a wrapper, you should be able to open it in a text editor and 
have a look.