Hi folks again,
I have since tried a few things and finally found an abnormality in the issues i faced so far.
1) I can compile successfully NSIS with the correct files and all, install that and run. The recent versions i got to work are: 22655 and 22706 (yesterday's).
2) There have been times when first compilation fails (at a few places), and after retrying it, it works (w/o the need to re-download or even doing anything).
The first that fails is:
a. When doing the \base\archives.bat, i did the whole batch file in a separate CMD dos windows. I went thru the batch logs slowly and realised that sometimes, the file is 'locked' and cannot be modified, hence the reason that batch files = successful, BUT actually, the various PK3 files are NOT successful.
What i meant is this:
archives.bat activated.
archives.bat starts with this commend ->
7za a -tzip 0base.pk3 *.cfg irc_motd.txt -x!".svn"
Then, because the file is locked, it says, not successful or file in use....
moves on and repeats same error.....
I ended up with alot of .pk3.tmp or .pk3.tmp1(2 3 4 5) files...
My workaround for this to be ok is this:
a. Delete all pk3 files before starting my archives.bat.
b. run the archives.bat
My recommendations for the original script \base\archives.bat is simply to add one more command before running the remaining script ->
"del *.pk3*"
Another workaround would be to modify the archives.bat this way:
a. Instead of using the -a switch, use the -u switch.
-a is to add files, but if they are already present (like in my case), they are skipped in a sense.
-u is to force update of all files which has changed.
Though i still prefer the previous, delete pk3 files method. Haha. This way, though the rebuilding takes a slightly longer time, it ensures that all files are "NEW" and updated.
PS: I am still deleting all pk3 files from now though before running the archives and NSIS script.
The next thing that fails is:
I realised as per the previous entries in this thread:
A) I did realised that radiant Dll files are not in place during this download, and that i have to manually extract (\contrib\dlls\radiant_runtime.zip) and put them into the directory (\radiant), esp so, in order for the nsis script (\src\ports\windows\installer.nsi) to run successfully.
Otherwise, it would die on line 237, since the CB did not code that (RADIANT) issue successfully.
This is definately the case. We need to perhaps modify the script so that \contrib\dlls\radiant_runtime.zip is unzipped into \radiant for \src\ports\windows\installer.nsi to work properly. Perhaps it can be with an 'overwrite' switch?
Last issue is perhaps with the NSIS "test installer" thing. Many times i tested the installer (which always install correctly - since the NSIS script runs thru), it is ok, only to start the game with this missing / that missing errors. Its sorta misleading.
Perhaps in future documentations, this point could be inserted and warn compilers like myself. lol.
Okie, time to think abt working the wiki. Sorry for my suddenly busy schedules due to microsoft updates and various updates from real life work. I am still here, hehe. Will continue beta testing once my silly schedules get back in routine.