NSIS 3.0b3

[Anders]

If you find any new issues, report them in this thread and/or on the SF bug tracker and please include compiler error messages and sample code if possible...

[meoit]

WOW!. I never thought that was an update earlier than I expected.

[noisehole]

There appears to be a syntax error in WinMessages.sh:

Usage: !define [/ifndef | /redef] ([/date|/utcdate] symbol [value]) | (/file symbol filename) | (/math symbol val1 OP val2)
OP=(+ - * / << >> >>> % & | ^)
!include: error in script: ".../Include/WinMessages.nsh" on line 102
!include: error in script: ".../Contrib/Modern UI 2/MUI2.nsh" on line 25
!include: error in script: ".../Include/MUI2.nsh" on line 1

moving the few "/math" starting at line 102 in front of the symbol names fixes it.

[TrifonovS]

Today I installed NSIS V3.0b3. When I tried to compile my old scripts I got the following error:

!include: "C:\Program Files (x86)\NSIS\Include\StrFunc.nsh" (UTF8)
!define: "_STRFUNC_CREDITVERBOSITY" already defined!
!include: error in script: "C:\Program Files (x86)\NSIS\Include\StrFunc.nsh" on line 15

If I revert to NSIS V3.0b2 I can compile my scripts again without this error. What can be the reason?

[JasonFriday13]

Today I installed NSIS V3.0b3. When I tried to compile my old scripts I got the following error:


If I revert to NSIS V3.0b2 I can compile my scripts again without this error. What can be the reason?

Trunk commit 6616 added this line:

!define _STRFUNC_CREDITVERBOSITY ${STRFUNC_VERBOSITY} 

Really it should look like this:

!ifdef _STRFUNC_CREDITVERBOSITY
  !undef _STRFUNC_CREDITVERBOSITY
  !define _STRFUNC_CREDITVERBOSITY ${STRFUNC_VERBOSITY}
!endif 

[Anders]

There appears to be a syntax error in WinMessages.sh:

moving the few "/math" starting at line 102 in front of the symbol names fixes it.

This was a bug in 3.0b2 not 3.0b3?

[Anders]

Today I installed NSIS V3.0b3. When I tried to compile my old scripts I got the following error:


If I revert to NSIS V3.0b2 I can compile my scripts again without this error. What can be the reason?

Thanks, fixed. This only happens when StrFunc.nsh is included multiple times.