From maintainers-request at octave dot org Mon Jan 9 10:48:39 2006 Subject: Re: Successful compilation with MinGW From: Shai Ayal To: Andy Adler Cc: octave maintainers mailing list Date: Mon, 9 Jan 2006 18:47:02 +0200 This is surprising! So, Andy, would it be safe to say that providing an octave installer for windows is only a "time" problem -- i.e. someone would have to invest the time but there are no "technological" problems? would the following procedure work? 1. get current octave & octave-forge precompiled cygwin packages and dependencies 2. get current cygwin1.dll and binary edit it to replace "Cygnus Solutions" as the registry key. 3. gather all other packages (gnuplot etc..) which could be the same as in your 2.1.42 package 4. slightly modify your NSIS script to account for any changes 5. produce a nice octave installer just like window users like. It will be self contained and will not affect any preinstalled cygwin Shai On 1/9/06, Andy Adler wrote: > On Mon, 9 Jan 2006, Shai Ayal wrote: > > > I think that including a cygwin1.dll in a "nice" windows installer is > > not that hard. From what I remember, the problem pops up when you > > already have another version of the cygwin1.dll installed you get very > > bad conflicts since they seem to relay on version independent registry > > entries-- i.e. installing octave+cygwin.dll in a system with cygwin > > already installed would break the old cygwin installation. > > > > If we were able to get around this problem, a one-step windows > > installer would be possible. > > > It is not hard to write a special cygwin1.dll that does not conflict. > The easist way is to binary edit it to replace "Cygnus Solutions" as > the registry key. > > In the 2.1.42 windows version I provided, the reg key was "GNU Octave. > http://www.site.uottawa.ca/~adler/octave/index.html > > -- > Andy Adler 1(613)562-5800x6218 >