http://bugzilla.wpkg.org/show_bug.cgi?id=232 Summary: WPKG 1.2's wrapper.js is broken Product: WPKG Version: other Platform: PC OS/Version: All Status: NEW Severity: normal Priority: P2 Component: wpkg.js AssignedTo: mangoo at wpkg.org ReportedBy: pastor at uni-mainz.de QAContact: wpkg-users at lists.wpkg.org wrapper.js from WPKG 1.2/tools/64-bit-wrapper is not working. In WPKG 1.2, wrapper.js now directly references the 64-bit cmd.exe: @@ -58,7 +58,8 @@ /** * Global variables */ -var cmd64="64-bit\\cmd.exe" +// var cmd64="64-bit\\cmd.exe" +var cmd64="%SystemRoot%\\sysnative\\cmd.exe" var wpkg="wpkg.js" However later in wrapper.js, var cmd64 is still used like if it would contain a path relative to wrapper.js: if (architecture != "" && architecture != "%ProgramFiles(x86)%") { // 64-bit system command += base + "\\" + cmd64 + " /c cscript " + base + "\\" + wpkg; As a quick fix, it is sufficient to remove 'base + "\\" + ' in front of cmd64. But this only works when actually called from 32-bit cmd on a 64-bit system. A more robust option could be to use %SystemRoot%\\sysnative\\cmd.exe when it exists, and otherwise revert to cmd.exe. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |