Re: [NSIS-devel] Several errors while I try to build Examples/makensis.nsi

[Oleksandr G. <gav...@gm...>]

On 2012-12-14, Anders wrote:

> When you build with UNICODE=yes the code that reads text files is in
> the C run-time so what happens actually depends on the version of
> Visual Studio and the Windows version.
>
Ok. So what MSVC version used to build official NSIS 3.0 release?

nsis-trunk/Docs/src/build.but suggest MSVC6 with February 2003 Platform SDK.

Link to MSVC 6.0 service pack 5 is valid but refer to web.archive.org. I found
official link to SP6 (which also have smaller size due to stripping OS
patches):

  http://www.microsoft.com/en-us/download/details.aspx?id=9183
                Service Pack 6 for Visual Basic 6.0, Visual C++ 6.0 with
                Visual Source Safe 6.0d

I think that appropriate text of 'build.but' may be updated...

Link for SDK is broken. This article:

  http://en.wikipedia.org/wiki/Microsoft_Windows_SDK#Versions

point to direct download links (from download.microsoft.com):

  http://social.msdn.microsoft.com/Forums/en/windowssdk/thread/e1147034-9b0b-4494-a5bc-6dfebb6b7eb1

Is that right tool-chain to build UNICODE NSIS?

I come to software development in late 2005 in time when

  http://blogs.msdn.com/b/publicsector/archive/2005/12/07/501169.aspx
                Visual Studio 6.0 removed from MSDN download on 12/16/2005

so I can't become legal user of MSVC 6... I fall into case of:

  http://en.wikipedia.org/wiki/Abandonware

How about MSVC Express editions? Are they supported for release build or we
have some limitations to do this?

What target OS list for NSIS?

Are there exist Microsoft discount program with images of Windows OS for free
or low cost to help independent developers?

> When building with MinGW it links to msvcrt.dll and so you probably
> need Vista+ for Unicode file support.
>
So this means that I can't perform release build with MinGW as users of WinXP
may have some problems?

> The hack used when building with UNICODE=no will probably go away.
>
Does this mean that 'UNICODE=no' become unsupported build configuration for
trunk?

> We need to fix the way we read text files before we can do a release...
>
I can help only with testing.

-- 
Best regards!