Development method

[David Hemmo]

Hello,

Right now, each time I make a modification (even one line) I do a 
'make' followed by a 'make install'.
Is there a faster way ?

Thanks

David Hemmo

[Mike McCormack]

David Hemmo wrote:
> Right now, each time I make a modification (even one line) I do a 'make' 
> followed by a 'make install'.
> Is there a faster way ?

Try skip the 'make install', and instead run wine from the build 
directory. eg.

~/src/wine/wine regedit

I make a point of never installing Wine to make sure I don't accidently 
run an older installed version that didn't get overwritten properly.

Mike

[Ivan Leo Puoti]

Mike McCormack wrote:
> Try skip the 'make install', and instead run wine from the build 
> directory. eg.
>
> ~/src/wine/wine regedit
>
> I make a point of never installing Wine to make sure I don't accidently 
> run an older installed version that didn't get overwritten properly.

You can also just have a script called wine in your path, that does something like

#!/bin/bash
/path/to/wine $*
just check you don't have other files in your path called wine.

Ivan.

[David Hemmo]

Ivan Leo Puoti wrote:
> Mike McCormack wrote:
> > Try skip the 'make install', and instead run wine from the build 
> > directory. eg.

I did it when I reinstalled Linux.
The downside is that make is still slower that if you do it in the 
directory where you made a modification.
The plus side is that it also works when you are modifying the server 
part of wine

I'll keep your solution

Thanks

David

[Stefan Dösinger]

Am Freitag, 8. April 2005 16:00 schrieb David Hemmo:
> Hello,
>
> Right now, each time I make a modification (even one line) I do a
> 'make' followed by a 'make install'.
> Is there a faster way ?

I run these commands in the directory of the dll or program which I changed. 
That is way faster(especially make install)

Stefan

[David Hemmo]

> I run these commands in the directory of the dll or program which I 
> changed.

Thats is way faster :-)

Thanks

David Hemmo