Benjamin Lindner wrote:
>
> Michael Goffioul wrote:
>> Well, the installer I wrote does a little bit more than simply unpacking:
>> - select components to install, with some auto-detection at startup
>> to select reasonable default config
>> - detect CPU architecture and auto-select ATLAS
>> - write start menu entries and desktop icon
>> - write registry entries to hold the install path: this is used by
>> add-ons installer to know where octave is installed
>> - manage dependencies for octave-forge packages
>
> Yes, I have discovered this in your .nsi script, and I agree, that it is
> quite comfortable, so I used some of your code for the mingw32 installer
> (start menu entries, cpu architecture & atlas).
>
Great, then I'd love to see it. If its ready for prime time we need to
think about the structure of the source-forge FRS for the new MinGW package
. The easiest would be is if like Michael you include all of the
octave-forge packages and then we remove the additional Windows packages
sub-project, rename the existing Windows sub-project to MSVC Windows and
create a new sub-project for MinGW Windows for you to upload to.
If you don't think its ready for prime time I can host it on my personal
machine as previously for testing purposes.
Regards
David
--
View this message in context:
http://www.nabble.com/Uploading-mingw32-octave-binaries---where-and-how--tp18141114p18305400.html
Sent from the octave-dev mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
