What happened to CVS binaries?

iceman_k
18th April 2005 05:45 UTC

What happened to CVS binaries?
I can't find MakeNSIS.exe or MakeNSISW.exe any more.
Does this have something to do with SCons?

deguix
18th April 2005 09:30 UTC

Yes. You can find them on nighly developed snapshots for now, but not to the latest.

I just don't know what will happen to NSIS Update:
- Will it be updated to download dev. snapshots?
- Will kichik separate the binaries from dev. snapshots to create a binary only dev snapshot?
- Or will he host binary files somewhere on nsis.sf.net?
- More?

kichik
19th April 2005 18:31 UTC

The executables were removed from CVS because that's just not their place. I've uploaded them by mistake to CVS at first but kept doing it because it allowed people to skip compiling NSIS. However, now that there's a very easy way to compile the entire NSIS package (well, except the Math plug-in, the Library registration tool and the NSIS Menu), there's no longer need for it. All you need is a compiler (Microsoft Visual C++ Toolkit 2003 and the Platform SDK, which are both free, are good enough) and SCons. If you don't want to install Python for SCons, see this page.

The nightly development snapshots no longer contain the executables as they are still just a simple CVS dump. I hope to get an automated build up soon, but I don't have a Windows computer which is constantly running and am having a hard time running cl.exe on WINE.

I still don't know what I'm going to do with NSIS Update. It'll probably allow you to download a real nightly snapshot which also contains compiled sources. Having it update from CVS is no longer useful, so that'll surely go away at some point.

iceman_k
19th April 2005 22:11 UTC

OK, fair enough.
I downloaded SCons.
I have MSVC++ 2003 Toolkit and Platform SDK.
What next?'
I made sure that the appropriate paths and environment variables were set by running vcvars32.bat for VC++ 2003 Toolkit and registering the PSDK directories as well.
I then tried running Scons and got a bunch of errors:


C:\projects\NSIS>"\Program Files\SCons\scons.exe"
scons: Reading SConscript files ...

scons: warning: Ignoring missing SConscript 'SCons\Config\ms'
File "SConstruct", line 73, in ?
TypeError: unsubscriptable object:
  File "C:\Program Files\SCons\scons-local-0.96.1\SCons\Script\__init__.py", line 1103:
    None
  File "C:\Program Files\SCons\scons-local-0.96.1\SCons\Script\__init__.py", line 1097:
    None
  File "C:\Program Files\SCons\scons-local-0.96.1\SCons\Script\__init__.py", line 903:
    None
  File "C:\Program Files\SCons\scons-local-0.96.1\SCons\Script\SConscript.py", line 239:
    None
  File "SConstruct", line 79:
    None

Apparently some additional configuration is needed before Scons can do its magic.

kichik
19th April 2005 22:27 UTC

I have created a news item on the website that explains how to compile using the toolkit, mingw and the usual vc. Take a look at it:

http://nsis.sourceforge.net/index.ph...=17&tt_news=22

SCons doesn't yet support the toolkit out of the box, so you have to tell it to use the toolkit by adding MSTOOLKIT=yes on the command line.

iceman_k
20th April 2005 02:53 UTC

With the windows compiled binary:


C:\projects\NSIS>"\Program Files\SCons\scons.exe" -j4 MSTOOLKIT=yes
scons: Reading SConscript files ...

scons: *** No tool named 'mstoolkit': No module named mstoolkit
File "SConstruct", line 66, in ?

Using python:


C:\projects\NSIS>\Python23\scons -j4 MSTOOLKIT=yes
scons: Reading SConscript files ...

scons: *** No tool named 'mstoolkit': No module named mstoolkit
File "SConstruct", line 66, in ?

So where can I get the mstoolkit module?

[edit]
Never mind- I had to update CVS to fetch the new Scons directory.
I got a few warnings and it craps out if hhc.exe is not in the path.

Just curious- what is the advantage of scons over regular make?

For the record, these are the warnings I get:


Contrib\System\Source\Buffers.c(49) : warning C4047: 'function' : 'int' differs in levels of indirection from 'HANDLE'
Contrib\System\Source\System.c(636) : warning C4047: '=' : 'int' differs in levels of indirection from 'HANDLE'
Contrib\System\Source\System.c(636) : warning C4047: '=' : 'HANDLE' differs in levels of indirection from 'int'
Contrib\System\Source\System.c(644) : warning C4047: '=' : 'int' differs in levels of indirection from 'char *'
Contrib\System\Source\System.c(653) : warning C4244: '=' : conversion from '__int64' to 'int', possible loss of data
Contrib\System\Source\System.c(934) : warning C4090: '=' : different 'volatile' qualifiers

[/edit]

WebMatze
20th April 2005 08:26 UTC

Scons
Hello i tried the new scons system and i got an error with the command
GetLaunchDir() and Environment().
I dont understand what's wrong,
I installed the standalone scons and added it to the path, then tried scons -j4...
I hope you can help me

bye

iceman_k
20th April 2005 13:50 UTC

Attach the error log. Which compiler are you using?

deguix
20th April 2005 17:01 UTC

This system is great. The problem is the number files that appear after you compile, like the build and .sconf_temp folders... I recommend some "os.remove(paths)" lines after compilation.

iceman_k
20th April 2005 18:22 UTC

A lot of the files it creates (e.g., in build) are for caching - so that it doesn't have to build them again.

deguix
21st April 2005 02:55 UTC

Oh, the "-c" parameter does exactly that in the command-line.

kichik
21st April 2005 16:22 UTC

iceman_k, the benefits of scons over make are described under "What makes SCons better?" in www.scons.org better than I could describe them.

deguix, unlike the old method, all of the build files are under one directory, which is much cleaner. But unlike the old build system, this one can install only the built stuff into another directory. It doesn't work perfectly in the current version I've uploaded, but soon enough, all you'd have to do to install NSIS from source is execute:

scons -j4 --random install PREFIX="C:\Program Files\NSIS"

deguix
21st April 2005 17:21 UTC

Thanks, looking foward to it.