> Is best practice to confine these to a particular folder (like you get
> with -fprofile-dir)? Is there a switch to do that for gcov data?
Due to limitations of my patch -fprofile-dir (or passing arguments to
-fprofile-* is unsupported). All it allows you can do is pass
"--coverage", "-fprofile-
On 06/22/2010 11:03 AM, Alexandre Julliard wrote:
> Peter Davies writes:
>
>> @@ -79,6 +79,9 @@ my @ignores = (
>> "*.ok",
>> "*.res",
>> "*.so",
>> +"*.gcno",
>> +"*.gcov",
>> +"/conf*",
>
> They are not generated by a standard build so they don't belong
> here. Put t
d into it, it seems that these files are usually deleted
by 'make depend' and are only temp files (I probably stopped "make
depend" with ^C to generate them).
The pattern is broken anyway since it also catches "configure", etc.
Peter
Peter Davies writes:
> Does this mean that "make depend" should be removed from README and
> ./tools/wineinstall? It generates /conf* files.
It shouldn't. What conf* files do you see?
--
Alexandre Julliard
julli...@winehq.org
Does this mean that "make depend" should be removed from README and
./tools/wineinstall? It generates /conf* files.
Peter
Peter Davies writes:
> @@ -79,6 +79,9 @@ my @ignores = (
> "*.ok",
> "*.res",
> "*.so",
> +"*.gcno",
> +"*.gcov",
> +"/conf*",
They are not generated by a standard build so they don't belong
here. Put then in your local ignore file.
--
Alexandre Julliard
julli...@win
On 14 June 2010 18:54, Peter Davies wrote:
> On 14 June 2010 18:40, Damjan Jovanovic wrote:
>>
>> Since around 2-3 months ago, you don't need to run "make depend" at all :-).
>>
>> Damjan
>>
>
> Then why is it still there?
When you run `mak
On Mon, Jun 14, 2010 at 8:54 PM, Peter Davies wrote:
> Then why is it still there?
I think it's still used internally. If you run `make depend' then
'make' you'll see it will go a bit faster because the dependencies are
already precomputed.
Octavian
On 14 June 2010 18:40, Damjan Jovanovic wrote:
>
> Since around 2-3 months ago, you don't need to run "make depend" at all :-).
>
> Damjan
>
Then why is it still there?
Peter
On Mon, Jun 14, 2010 at 6:52 PM, Peter Davies wrote:
> How often do I need to run "make depend"?
>
> Peter
>
>
>
Since around 2-3 months ago, you don't need to run "make depend" at all :-).
Damjan
How often do I need to run "make depend"?
Peter
On 6 Oct 2004, Vincent [ISO-8859-1] Béron wrote:
> Le mer 06/10/2004 à 18:13, Michael Stefaniuc a écrit :
> > On Thu, Oct 07, 2004 at 12:46:35AM +0200, Saulius Krasuckas wrote:
> > > | make[1]: Entering directory `/mnt/antras/usr/src/wine-cvs/wine/include'
> > > | ../tools/widl/widl -I. -I. -I../in
Le mer 06/10/2004 à 18:13, Michael Stefaniuc a écrit :
> On Thu, Oct 07, 2004 at 12:46:35AM +0200, Saulius Krasuckas wrote:
> > It may be redundant info, but whatever. An excerpt from the output:
> >
> > | Configure finished. Do 'make depend && make' t
On Thu, Oct 07, 2004 at 12:46:35AM +0200, Saulius Krasuckas wrote:
> It may be redundant info, but whatever. An excerpt from the output:
>
> | Configure finished. Do 'make depend && make' to compile Wine.
> |
> | cd include && make all
> | make[1]:
It may be redundant info, but whatever. An excerpt from the output:
| Configure finished. Do 'make depend && make' to compile Wine.
|
| cd include && make all
| make[1]: Entering directory `/mnt/antras/usr/src/wine-cvs/wine/include'
| ../tools/widl/widl -I. -I.
>...
> FYI, I haven't managed to complete the make procedure anyway. It seems that
> the 2.6.0 kernel headers (/usr/include/linux/) wrt. the scsi ones have some
> trouble:
> gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_NTSYSTEM_
> -D_REENTRANT -fPIC -Wall -mpreferred-stack-bound
Joerg Mayer <[EMAIL PROTECTED]> writes:
> Wouldn't it make more sense to ask the authors of the artsc-config script
> to fix it?
We can do that too, but it won't help for existing installations, so
we need a fix anyway.
--
Alexandre Julliard
[EMAIL PROTECTED]
On Sat, Jan 03, 2004 at 10:02:10AM -0800, Alexandre Julliard wrote:
> "P. Christeas" <[EMAIL PROTECTED]> writes:
>
> > I thought of that when I was trying to see why the make had been broken.
> > Unfortunately, the artsc-config script is not within "our" reach. Isn't the
> > makedep utility supp
"P. Christeas" <[EMAIL PROTECTED]> writes:
> I thought of that when I was trying to see why the make had been broken.
> Unfortunately, the artsc-config script is not within "our" reach. Isn't the
> makedep utility supposed to have compiler's options as parameters?
No, how could it? There's no
> "P. Christeas" <[EMAIL PROTECTED]> writes:
> > On my configuration, the 'artsc-config' script outputs '-pthread' along
> > with the '-Isth' entries. That broke the 'makedep' procedure.
> > It's trivial. The following patch handles this.
>
> The right fix is to get rid of that option at configure
"P. Christeas" <[EMAIL PROTECTED]> writes:
> On my configuration, the 'artsc-config' script outputs '-pthread' along with
> the '-Isth' entries. That broke the 'makedep' procedure.
> It's trivial. The following patch handles this.
The right fix is to get rid of that option at configure time (or
On my configuration, the 'artsc-config' script outputs '-pthread' along with
the '-Isth' entries. That broke the 'makedep' procedure.
It's trivial. The following patch handles this.
Index: makedep.c
===
RCS file: /home/wine/wine/tool
22 matches
Mail list logo
