MikeSchinkel
19th December 2005 04:28 UTC
Why require a recompile for NSIS_CONFIG_LOG?
May I ask why the developers chose to make this require a recompile? It seems like it only invites forking, and will break installs if someone upgrades NSIS to a more current version but doesn't first recompile with NSIS_CONFIG_LOG changed. This can cause much confusion when the person doing maintenance isn't the one who originally wrote it, so there must have been a really good reason to require it to work this way?
Also, Joost Verburg says you can log more with this modification. Can someone elaborate on what this allows to be logged that can't otherwise be logged?
Thanks in advance.
DrO
19th December 2005 09:51 UTC
i'm not entirely sure on what is logged (i believe it's most file actions, etc being carried). the reason for it being off by default is to keep the installer's stub size down (which is one of the main ethos's behind nsis)
-daz
Afrow UK
19th December 2005 09:53 UTC
You don't really have to recompile NSIS. Special builds are available for download from the NSIS homepage.
-Stu
MikeSchinkel
20th December 2005 04:36 UTC
Originally posted by Afrow UK
You don't really have to recompile NSIS. Special builds are available for download from the NSIS homepage.
-Stu
Ah thanks, that's better.
onad
20th December 2005 12:10 UTC
Adding debug logs makes the installer bigger, that why it is off by default.
An NO there are no new "Forks" needed the code to add logs is IN the default source head always, only a recompile is needed Which you can no do relativly easy if you read the instructions.
But ofcouse you can use the special builds.
success
gultig
19th April 2006 18:12 UTC
Is it possible that the use of LogText issues a warning rather than an error if NSIS_CONFIG_LOG is not defined?
kichik
19th April 2006 18:33 UTC
No, but you can use !ifdef NSIS_CONFIG_LOG.
Comm@nder21
20th April 2006 18:25 UTC
what about a compiler setting giving the user the choice between warnings/errors for uncompiled commands?