Compiling and Saving a Module, outside of toolset?

[Legacy_virusman]

               ---
               
               

               

                     Modifié par virusman, 14 janvier 2011 - 03:16 .
                     
                  

            

[Baaleos]

               Yeah, I know Areas has been multiplatform, but I think you first developed it on Windows, Im just remembering back to the forum post on nwnx, where you said something like 'Will port to Linux later today' or something.



I know they were both released more a less on the same day, but I thought you did the initial work on windows, then ported to Linux.
               
               

               
            

[Legacy_Sysnn]

               I actually use SVN on my 1000+ script of my module.



- I have a versioned SVN copy of all my scripts in a folder.



- everytime I get an updated module:



+ open it by Aurora



+ run a batch file that delete every .nss from my SVNed folder, and copy all *.nss from <nwn>\\modules\\temp0 into this folder.



+ verify the changes (and add any new script to the repository), and commit the update.



+ update the needed .nss in the SVN folder.



+ run a batch file that deletes all *.nss & *.nsc files into <nwn>\\modules\\temp0, and copy all versioned/updated *.nss in this folder.



+ return to Aurora, and save the module, close module & reopen it from aurora and compile all scripts, and save the module again.





To work directly into SVNed scripts outside Aurora, I use a Notepad++ & PRC script compiler.

Using C# syntax highlighting is it possibile to use a plugin with the function list.





Actually I have 2 SVN folders:



+ one for the develop/debugging activities (with a small custom module version).



+ one for the 'production' modules script.





I hope it may help.  '>
               
               

               
            

[Baaleos]

               Yeah, I use svn too, for the module as a compiled entity, but as it gets bigger and bigger, it will become harder to sustain and upload etc.



Eg - Scripts etc, only take a few bytes of data transmission, but areas and creatures and items, usually require the entire binary to be uploaded.

I dont fanci the day when the module moves to 100+ mb in size and having to do a svn comitt.
               
               

               
            

[Legacy_FunkySwerve]

               That's precisely why we split the mod, diffing, and only transferring changed bits, rather than doing the whole mod at a go - our mod is 157M or so.



Funky
               
               

               
            

[Legacy_ehye_khandee]

               Is there some size limit that has been hit where the toolkit no long can manage the module and/or BUILD well? Our module is 187mb, and I do the build on my Acer Aspire One notebook - it takes less than five minutes last time I timed it. It has atm almost 4100 scripts (nss files) in it, and over 1250 Areas. I normally only do a BUILD on the palettes and scripts (we don't use encounters and creature CR we only occasionally do a build on) - the build takes less than five minutes in these circumstances.



What are the rest of you builders experiencing in this regard? Can we compare notes please?