3.0 when?

Benjamin Lindner lindnerben at gmx.net
Mon Jan 7 14:55:40 CST 2008


Tatsuro MATSUOKA wrote:
> Hello Michael and jwe.
> 
> Michael> Why not also package octave-forge in the mingw binaries?
> 
  > I do not want my mingw binaries to be official release.
> Perhaps Benjamin will provide the official release at octave-forge.

Yes, I hoped to do so.

> Yesterday I saw Benjamin's svn repository.  It seems that he is now extesively preparing the next
> release.

Aha, got me :)
I have tried the new mingw32 gcc-4.2.1 release, which provides now 
shared libstdc++ and shared libgcc. With a 2.9.17 version is works.
The main advantage (aside from the newer compiler) is smaller libs and 
smaller oct files, since you do not statically link libstdc++ into every 
oct file.
Besides, the gcc-3.4.5 is rather ancient, e.g. I couldn't compile 
pcre>7.0 because of ICEs.
However, the mingw people name the 4.2.1 'technology preview' so it 
might be not yet too stable.
I will provide both gcc-3.4.5 compiled and gcc-4.2.1 compiled binaries, 
and let others try also.

> 
> The concept of my mingw binaries are to distribute the latest Windows native binary
> as early as possible because of the building process octave itself on mingw is now quite easy.

Exactly.
The dependency building is rather non-trivial and also took most of my 
time up to now to get it consistent and reproducible...

benjamin


More information about the Octave-maintainers mailing list