micahel
13th August 2003 09:42 UTC

NSIS_CONFIG_LOG how and where to define?
Hi,

I have another question regarding the logging. The docs say:

4.9.12.1 LogSet
on|off
Sets whether install logging to $INSTDIR\install.log will happen. $INSTDIR must have a value before you call this function or it will not work. Note that NSIS_CONFIG_LOG must be set in the installer configuration (it is not by default) to support this.

Here my question:
How can I set the NSIS_CONFIG_LOG ?
Where shall I set it ? In the script file of MY installer-script or in the config files of NSIS?

Thanks
Michael

Sunjammer
13th August 2003 10:23 UTC

You missed the line after that says "Note that NSIS_CONFIG_LOG must be set in the compile configuration file (config.h) on compile time (it is not by default) to support this. See Compiling NSIS Sources for more information about recompiling NSIS.". So like it says see Compiling NSIS Sources.

[edit]Actually maybe it's just that the online docs are slightly more recent than your copy[/edit]

micahel
13th August 2003 12:28 UTC

Ah, sorry,

I read my locally installed Docs which came with the build version NSIS v2.0b3.
I don't use the sources, so sorry for the confusion and thanks anyway for your help.

Cheers, Michael

mdm
14th August 2003 16:09 UTC

Wait...I don't get what you've agreed upon. Yes I changed ~NSIS\Source\exehead\config.h (uncommented #define NSIS_CONFIG_LOG). Now I gather that I recompile this source code.

Could you tell me exactly how to do that; where is the workspace, the .dsw, that I need to recompile. Or maybe I'm wrong on this and if so, can you re-steer me?

thanks,
mdm

Joost Verburg
14th August 2003 16:13 UTC

Which compiler do you have?

mdm
14th August 2003 22:33 UTC

Microsoft Visual C++ 6.0

Joost Verburg
14th August 2003 23:28 UTC

That's easy. Just open the project file and choose Batch build from the Build menu.

mdm
15th August 2003 17:32 UTC

thanks, looks like it recompiled. now have to figure out if install.log is a default or do I define it

:o mdm

brodbeck
15th August 2003 19:45 UTC

Alternative to recompile NSIS
Another alternative is to use a function to dump the contents fo log window to a file.

See in:
http://nsis.sourceforge.net/Docs/AppendixC.html
the item C.6 Dump Content of Log Window to File.

Good Luck

Joost Verburg
15th August 2003 20:06 UTC

You won't get the same result. With NSIS_CONFIG_LOG you can log a lot more.

mdm
15th August 2003 22:37 UTC

quite a bit more..I found some root of some mysterious errors in file initialization with it. By the way, what is Call:<int_value> and Jump:<int_value>?

mdm

Sunjammer
16th August 2003 19:51 UTC

Probably (but not definitely) Call is invocation of a function, and Jump is a goto.

mdm
18th August 2003 17:36 UTC

thanks,
mdm

jmu66@yahoo.com
4th January 2006 01:20 UTC

where can I download the source code for this?
where can I download the source code for this?

Afrow UK
4th January 2006 16:20 UTC

No need to recompile the source. Download the special build with logging enabled from:
http://nsis.sourceforge.net/Special_Builds

-Stu

Jackm
4th January 2006 23:43 UTC

thanks.
what difference between this makensis with original one?

kichik
5th January 2006 16:46 UTC

makensis also needs to change to support logging. For example, it needs to support the LogSet command.

vinnietran
1st November 2006 22:46 UTC

Afrow UK. You've posted special build for Logging. Too much information in the install.log, anyway I can simplify that?

Thanks.

kichik
1st November 2006 22:51 UTC

You'll have to change the code and rebuild NSIS yourself to modify or remove log messages.