[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re: Poor plot performance on Windows
From: |
PhilipNienhuis |
Subject: |
Re: Re: Poor plot performance on Windows |
Date: |
Thu, 17 Mar 2016 07:45:56 -0700 (PDT) |
tmacchant wrote
> --- pr.nienhuis
>> tmacchant wrote
>> > ----- Original Message -----
>> >
>> >> From: Mike Miller
>> >> To: Jake
>> >> Cc: Help GNU Octave
>> >> Date: 2016/3/17, Thu 15:23
>> >> Subject: Re: Poor plot performance on Windows
>> >>
>> >> Personally I am interested in helping make Octave as stable and
>> portable
>> >> as possible. I test and fix bugs on a wide range of GNU/Linux and UNIX
>> >> systems even though I personally only use Debian.
>> >>
>> >> I want Octave to be just as useful and stable on Windows as it is on
>> >> Debian. I have no access to a Windows system to help make that happen,
>> >> so all I can do is make suggestions for others to try and ask for test
>> >> cases and debugger stack traces.
>> >
>> >
>> > Perhaps mxe-octave can build octave for windows with debug symbols.
>> > Am I right?
>> > (However the package size will be huge.)
>> >
>> > If it is possible I will try to build octave for windows with debug
>> symbol
>> > and will upload on my web site.
>>
>> Tatsuro,
>>
>> Building an unstripped windows binary is easy - in principle.
>>
>> But yes it will be huge, last time I made one it was around 990 MB.
>> In addition, you can't make an installer, merely a zipdist, as the size
>> of
>> all files will probably exceed NSIS' 2 GB limit (it did in my case).
>> Excluding the OF packages may help a little bit but not enough to avoid
>> the
>> NSIS limits.
>>
>> Philip
>
> Philip , thanks for your information. As expected, it bocomes huge size
> binary.
>
> I am planning to use 7-zip ed file to reduce size. Is there options for
> the debug build?
> Or I have to specify like the CC='gcc -g' ? in configure?
What I can suggest is to just make the zipdist, and when finished, zip up
the <mxe-octave/dist/octave-<date-time> subdir (there's a complete Octave
installation in there) with max. compression.
Still it will be huge.
Maybe it is possible to just leave Octave itself unstripped (the octave
.exe's + the 3 liboct*.dll's + the .oct files) but do strip Octave's
dependency libraries and support (MingW/MSYS) utilities in bin/? (just a
hunch)
I really don't know about the other binary files (.a, .la and .o files).
Philip
--
View this message in context:
http://octave.1599824.n4.nabble.com/Poor-plot-performance-on-Windows-tp4675531p4675601.html
Sent from the Octave - General mailing list archive at Nabble.com.
- Re: Poor plot performance on Windows, (continued)
- Re: Poor plot performance on Windows, Nicholas Jankowski, 2016/03/16
- Re: Poor plot performance on Windows, Jake, 2016/03/16
- Re: Poor plot performance on Windows, Nicholas Jankowski, 2016/03/16
- Re: Poor plot performance on Windows, Jake, 2016/03/16
- Re: Poor plot performance on Windows, tmacchant, 2016/03/16
- Re: Poor plot performance on Windows, Mike Miller, 2016/03/17
- Re: Poor plot performance on Windows, Tatsuro MATSUOKA, 2016/03/17
- Re: Poor plot performance on Windows, PhilipNienhuis, 2016/03/17
- Re: Poor plot performance on Windows, tmacchant, 2016/03/16
Re: Re: Poor plot performance on Windows, address@hidden, 2016/03/17
- Re: Re: Poor plot performance on Windows,
PhilipNienhuis <=