Hello readers,
Does anyone know how to get NSIS compiler version in compile time, on 2.0b3/4? I'd like to use it for conditional compiles, especially for working around 2.0b3 win95/me garbling bug.
I've looked into documents, FAQs, forums, but I couldn't find any light shed on it.
Thanks in advance.
Getting NSIS version
6 posts
Which bug are you talking about?
I think it's better to distribute the latest version with your script. Making your script compatible with different versions isn't that easy and will take a lot of time.
I think it's better to distribute the latest version with your script. Making your script compatible with different versions isn't that easy and will take a lot of time.
You can get the version using makensis.exe /VERSION but you can't parse it on compile time, !system supports only return value comparsions.
Er... Thanks for your quick reply 🙂
I was talking about the one marked #707476 (Japanese woes) on sourceforge.net.
Anyways.. OK I see your point: Probably I release my software with latest stable version of NSIS.
But I think such a feature is not so awful to have, especially for quick working around or something.
(I was really trying to fix the bug using 2.0b4, but it won't allow MUI_FONTs anymore, and it isn't released yet. Additionally 2.0b3 contains some wierd language I fixed.. 😉)
I didn't meant something like dancing #ifdefs in sources of "portable" programs. I agree such a usage will be nightmare 😉
I was talking about the one marked #707476 (Japanese woes) on sourceforge.net.
Anyways.. OK I see your point: Probably I release my software with latest stable version of NSIS.
But I think such a feature is not so awful to have, especially for quick working around or something.
(I was really trying to fix the bug using 2.0b4, but it won't allow MUI_FONTs anymore, and it isn't released yet. Additionally 2.0b3 contains some wierd language I fixed.. 😉)
I didn't meant something like dancing #ifdefs in sources of "portable" programs. I agree such a usage will be nightmare 😉
Please explain why you can't fix the bug with 2.0b4. It still contains the same font settings.
Argh! I found it was my fault. Having reordered includes as MUI's README stating, it started to work again. Shame on me.
Sorry for the hassle.
Sorry for the hassle.