On Mon, Apr 20, 2009 at 10:04 PM, John W. Eaton <j...@octave.org> wrote: > FWIW, I would prefer it if the primary Octave binaries for Windows > were built with MinGW. That way we wouldn't have these problems. But > if you (Michael) want to distribute binaries built with VC++, then > wouldn't it be better to stop distributing the VC++ libraries (have > the user install them separately, if needed) instead of eliminating > the GiNaC/CLN libraries from your installer?
To be honest, I'm pissed off by all these licensing stuffs. I won't make any new Windows/VC++ release and I'll stop supporting compiling octave with VC++. I'll leave to Benjamin the work of making Windows binaries with MinGW. I've removed the VC++-compiled packages from SF.net. Bye, Michael. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
