scons duplicate environment warnings on Windows
Bug #1151646 reported by
Sean M. Pappalardo
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Low
|
RJ Skerry-Ryan | ||
| 1.11 |
Won't Fix
|
Low
|
Unassigned | ||
| 2.0 |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
When building recent versions of the 1.11 branch (I don't know exactly when this started because I've been away for awhile,) scons reports the following error on all Soundtouch files:
scons: warning: Two different environments were specified for target C:\Mixxx\
but they appear to have the same action: ${TEMPFILE("$SHCXX $_MSVC_OUTPUT_FLAG /c $CHANGED_SOURCES $SHCXXFLAGS $SHCCFLAGS $_CCCOMCOM")}
File "C:\Mixxx\
It persists even if I delete scons' cache and the build directory (doing a clean build.)
Nothing jumped out at me looking near that line in the SConscript.
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #1 |
| Changed in mixxx: | |
| status: | New → Fix Released |
| Changed in mixxx: | |
| status: | Fix Released → Triaged |
| tags: | added: build |
| Changed in mixxx: | |
| assignee: | nobody → RJ Ryan (rryan) |
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #2 |
| Changed in mixxx: | |
| status: | Triaged → In Progress |
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #3 |
Revision history for this message
| Sébastien BLAISOT (sblaisot) wrote | #4 |
| summary: |
- scons duplicate environment error on Windows + scons duplicate environment warnings on Windows |
| Changed in mixxx: | |
| assignee: | RJ Skerry-Ryan (rryan) → nobody |
| status: | In Progress → Triaged |
| Changed in mixxx: | |
| assignee: | nobody → RJ Skerry-Ryan (rryan) |
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #5 |
| Changed in mixxx: | |
| milestone: | none → 2.3.0 |
| status: | Triaged → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #6 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
I think I fixed this.