Issues 2008-12-17
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
|
 
Still loading...
ABCDEFG
1
IDVotesType/MemberMilestonePriOwnerSummary/Comments
2
3
19100DEFECTtriageP1issues@sconsRecursive flag ignored in dictionary based scanners
4
consensus
5
6
Bill
7
Brandon
8
David
9
Gary
10
Greguh, what?StevenIf he wants his scanner only to operate on his file suffix, he shouldn't specify it for .h files. If he wants his scanner to operate on both suffixes and it isn't, I believe it's a bug. However, from his followup, it appears that his scanner is operating on both suffixes as it should. Whichever, someone needs to contact OP and clarify. Steven to untangle? Maybe all it needs is better doc?
11
Jim
12
Ken
13
Sohail
14
StevenresearchstevenknightFigure out if it's a real bug
15
16
22490DEFECTtriageP2issues@sconsPCH source file rebuilt every time when certain filenames are used
17
consensus
18
19
Bill
20
Brandon
21
David
22
Gary
23
Greg???The first thing I'd do is remove the glob() and see if that fixes things. If it doesn't, I wouldn't know where to start looking. Assign it to a vs_revamp author for research?
24
Jim
25
Ken
26
Sohail
27
Stevenresearch??weird. smells like it might be an issue with drive letters, given the rather haphazard list of characters that do/do not trigger it
28
29
20840ENHANCEMENTtriageP4issues@sconsSupporting allow_undefined ala libtool to build libraries with undefined symbols
30
consensus
31
32
Bill
33
Brandon
34
David
35
Gary
36
GregOK, why did Gary return it to the pool? There's no comment with any kind of analysis.
37
Jim
38
Ken
39
Sohail
40
StevenfutureTBDLooks like David has a workaround, so future / lower priority
41
42
21900FEATUREtriageP4issues@sconsAutoconf Functionality: check existence of a file
43
consensus
44
45
Bill
46
Brandon
47
David
48
Gary
49
Gregfuure +keyword?Could be part of a replacement for Configure(), but we haven't talked about when that could be done.
50
Jim
51
Ken
52
Sohail
53
Stevenagree w/Greg
54
55
21960DEFECTtriageP4issues@sconsMisleading error message
56
consensus
57
58
Bill
59
Brandon
60
David
61
Gary
62
Gregfuturep2Sigh. Might be a minor speed optimization, but can keep.
63
Jim
64
Ken
65
Sohail
66
Stevenfuturep2#ERROR!
67
68
22610DEFECTtriageP4issues@sconsCommand() builder whose target is a directory is not rerun when sources change
69
consensusLeft over from last time. Steven said he'd like to take a crack at it since an untar into a directory ought to work if the source(s) changed, but we never discussed milestone or priority. (Why MP-complete as a nym, BTW?)
70
71
Bill
72
Brandon
73
David
74
Garyinvalidshould use target filename instead of dir
75
GreginvalidWorks as designed (and just like make)
76
Jim
77
Ken
78
Sohail
79
Stevenresearchsteveknightwe should be able to handle dirs as targets, at least better than we do now
80
81
22680DEFECTtriageP4issues@sconsscons -c fails if .sconsign.dblite is deleted
82
consensus
83
84
Bill
85
Brandon
86
David
87
Gary
88
Greginvalid?Someday, 'scons -ccc' will delete the .sconsign file(s). I wouldn't expect 'scons -c' to work if the .sconsign file(s) are deleted, but maybe I'm not understanding what he's asking.
89
Jim
90
Ken
91
Sohail
92
Steven2.xp3TBDagree w/Greg re: "some day" but you really should be able to get rid of the .sconsign files *some* way without seeing a stack trace...
93
94
22690ENHANCEMENTtriageP4issues@sconsReceive the builder command in a Decider
95
consensus
96
97
Bill
98
Brandon
99
David
100
Gary
Loading...
 
 
 
Sheet 1