Unicode

[MSG]

So, I guess it's unlikely that there will ever be a new version of NSIS, then?

[Anders]

Originally Posted by MSG

So, I guess it's unlikely that there will ever be a new version of NSIS, then?

We can still do ansi builds...

[pabs]

Originally Posted by Anders

We can still do ansi builds...

Except for on Linux (needs tchar.h)... hmm, mingw-w64 has tchar.h, I guess the cross-compile checks are in need of an update for the new toolchains.

[Anders]

Originally Posted by pabs

Except for on Linux (needs tchar.h)... hmm, mingw-w64 has tchar.h, I guess the cross-compile checks are in need of an update for the new toolchains.

I'm going to try to fix all the ansi problems, but I'm not sure if we should move to mingw-w64 or stick with the original. Anyways, we probably need our own tchar.h or hacks in platform.h since not all compilers/CRT agree on how swprintf works.

[noeld]

Hello all,

Is there any way to enable High-DPI awareness in an NSIS Unicode installer? Currently it seems to rely on display scaling in Windows 7 which does not look really good on high-DPI screens.

High-DPI awareness requires a manifest as describe in the article at:
http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx (Declaring DPI Awareness)

I tried to use mt.exe to apply the DeclareDPIAware.manifest but after that I get a message that the installer integrity check failed.

If this is not currently supported, could this be considered for an upcoming version? Thank you.

[Anders]

Originally Posted by noeld

Hello all,

Is there any way to enable High-DPI awareness in an NSIS Unicode installer? Currently it seems to rely on display scaling in Windows 7 which does not look really good on high-DPI screens.

You could try system::call 'user32::SetProcessDPIAware()' in .onInit, if that does not work you two other options:

A) Use !packhdr and resource hacker to change the manifest (Or maybe mt.exe, who knows)

B) Recompile from source

[noeld]

Thanks Anders,

system::call 'user32::SetProcessDPIAware()' in .onInit and un.onInit seems to work just fine. Some text looks a bit small but this should be ok for now.

[Anders]

Originally Posted by pabs

Except for on Linux (needs tchar.h)... hmm, mingw-w64 has tchar.h, I guess the cross-compile checks are in need of an update for the new toolchains.

I'm now able to compile (ansi) with MinGW, get latest source from SVN and add these changes:

--- SConscript-HEAD
+++ /trunk/Contrib/SubStart/SConscript Thu Jun 16 19:42:13 2011
@@ -9,8 +9,7 @@
libs = Split("""
""")

-Import('BuildUtil')
-
-substart = BuildUtil(target, files, libs)
-
-env.DistributeBin(substart, names=['makensis.exe'], alias='install-compiler') # install as makensis
+if env['PLATFORM'] == 'win32': #Using cross_platform = True just to force console app in PE header...
+ Import('BuildUtil')
+ substart = BuildUtil(target, files, libs, cross_platform = True)
+ env.DistributeBin(substart, names=['makensis.exe'], alias='install-compiler') # install as makensis

And you need to rename Call.S to Call.sx if you want to compile system.dll

I did not add the substart change to SVN since it is a bit of a hack, it would be better if we actually fixed the SCons stuff.

Not sure what to do about the Call.S issue, it might be SCons/MinGW version specific.