David Bateman wrote: > Michael Goffioul wrote: > > How easy would it be to adapt you NSI script to the MinGW package? I > also think it would be a good idea to wrap the compilers and the option > to install them in the installer as this is where the MinGW installer > will excel relative to the MSVC installer. > > Basically I know nothing above the NSI scripting language and avoided > learning it, but it seems that the MSVC and MinGW packages will be so > similar that the modifications in NSI for one or the other will be minimal. >
Hmm, I also currently have never worked with nsi scripts. I took a quick look at micheal's .nsi scripts in the repos and did not understand them at first, so I have to do some learning. I personally would have shamelessly extracted useful code from michael's script and adapted for the mingw32 package. I don't know which way is the easier: -) assuming that the msvc and mingw packages are similar, and adding effort (every time) to every difference that occurs -) adding effort to have seperate msvc and mingw scripts, taking advantage of michael's already available scripts I tend to use the second option. The packages are basically similar but there will be many different details (at least currently) - this may change over time, who knows. So I'd start with a rather simple installer with less options, only the ATLAS part, and a full octave installation (no options there). This can (and will) be improved over time. benjamin ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
