NSIS_CONFIG_LOG how and where to define?

micahel · 13th August 2003, 08:42

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, 09:23

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, 11:28

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, 15:09

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, 15:13

Which compiler do you have?

mdm · 14th August 2003, 21:33

Microsoft Visual C++ 6.0

Joost Verburg · 14th August 2003, 22:28

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

mdm · 15th August 2003, 16:32

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

mdm

brodbeck · 15th August 2003, 18:45

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, 19:06

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

mdm · 15th August 2003, 21:37

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, 18:51

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

mdm · 18th August 2003, 16:36

thanks,
mdm

4th January 2006, 00:20

where can I download the source code for this?

Afrow UK · 4th January 2006, 15:20

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, 22:43

thanks.
what difference between this makensis with original one?

kichik · 5th January 2006, 15:46

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

vinnietran · 1st November 2006, 21:46

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, 21:51

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

13th August 2003, 08:42	#1
micahel Junior Member Join Date: Aug 2003 Posts: 8	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

15th August 2003, 18:45	#9
brodbeck Junior Member Join Date: Aug 2003 Location: Taquara, RS, Brazil Posts: 2	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

4th January 2006, 00:20	#14
jmu66@yahoo.com Guest Posts: n/a	where can I download the source code for this? where can I download the source code for this?

5th January 2006, 15:46	#17
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	makensis also needs to change to support logging. For example, it needs to support the LogSet command. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

1st November 2006, 21:51	#19
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	You'll have to change the code and rebuild NSIS yourself to modify or remove log messages. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

13th August 2003, 09:23	#2
Sunjammer Major Dude Join Date: Jun 2002 Location: Swindon, UK Posts: 559	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]

13th August 2003, 11:28	#3
micahel Junior Member Join Date: Aug 2003 Posts: 8	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

14th August 2003, 15:09	#4
mdm Member Join Date: Jul 2003 Posts: 57	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

14th August 2003, 15:13	#5
Joost Verburg NSIS MUI Dev Join Date: Nov 2001 Posts: 3,717	Which compiler do you have?

14th August 2003, 21:33	#6
mdm Member Join Date: Jul 2003 Posts: 57	Microsoft Visual C++ 6.0

14th August 2003, 22:28	#7
Joost Verburg NSIS MUI Dev Join Date: Nov 2001 Posts: 3,717	That's easy. Just open the project file and choose Batch build from the Build menu.

15th August 2003, 16:32	#8
mdm Member Join Date: Jul 2003 Posts: 57	thanks, looks like it recompiled. now have to figure out if install.log is a default or do I define it mdm

15th August 2003, 19:06	#10
Joost Verburg NSIS MUI Dev Join Date: Nov 2001 Posts: 3,717	You won't get the same result. With NSIS_CONFIG_LOG you can log a lot more.

15th August 2003, 21:37	#11
mdm Member Join Date: Jul 2003 Posts: 57	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

16th August 2003, 18:51	#12
Sunjammer Major Dude Join Date: Jun 2002 Location: Swindon, UK Posts: 559	Probably (but not definitely) Call is invocation of a function, and Jump is a goto.

18th August 2003, 16:36	#13
mdm Member Join Date: Jul 2003 Posts: 57	thanks, mdm

4th January 2006, 15:20	#15
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	No need to recompile the source. Download the special build with logging enabled from: http://nsis.sourceforge.net/Special_Builds -Stu

4th January 2006, 22:43	#16
Jackm Junior Member Join Date: Jan 2006 Posts: 7	thanks. what difference between this makensis with original one?

1st November 2006, 21:46	#18
vinnietran Junior Member Join Date: Apr 2006 Posts: 20	Afrow UK. You've posted special build for Logging. Too much information in the install.log, anyway I can simplify that? Thanks.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode