Windows alwasy uses 0x5C as directory seperator even with codepages
that map this byte to a different character (unless it is part of a
multi-byte character). Specifically this affects Japanese (cp 932) and
Korean (cp 949) where the path seperator ends up as ¥ or ₩ respectively.
Fixes: issue #101
This implementation is based on the My Inno Setup Extensions changelog
http://web.archive.org/web/20010306024721/http://www.wintax.nl/isx/
as well as source for ISX version 2.0.10 and 3.0.6.1 plus some RE.
The oldest ISX version available to be tested was 1.3.10.
Fixes: issue #85
The previously supported "1.3.21" was really a misidentified 1.3.24.
This is mostly based on the Inno Setup changelog for version 1.3:
http://www.jrsoftware.org/files/is1.3-whatsnew.htm
Only installers for the following versions were available to be tested:
- 1.3.3
- 1.3.9
- 1.3.10
- 1.3.21
- Remove configure-time endianness check
(replaced by run-time check to be optimized out by the compiler)
- Move loading functions into the util namespace
- Only keep the setup header entries we actually need
* SET_WARNING_FLAGS for warning options (don't affect binaries)
* SET_OPTIMIZATION_FLAGS for compiler & linker optimization options
Also, re-enable some warnings that were disabled and instead suppress
them for the individual occurences.
Charles Pigott
UserUnknownFactor
Daniel Scharrer
Daniel Scharrer
Daniel Scharrer