[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: glob library, octave compilation on mingw
From: |
Benjamin Lindner |
Subject: |
Re: glob library, octave compilation on mingw |
Date: |
Wed, 09 Dec 2009 22:05:28 +0100 |
User-agent: |
Thunderbird 2.0.0.22 (Windows/20090605) |
Naveen Garg wrote:
The installer does not ship with the source code of
every library built as that's not the intended purpose
of a binary distribution.
How about shipping the intermediate install for a binary distribution
(developer version)?
Is is already included in the installer. The whole intermediate
installation tree is simply copied by the gcc44_install_deps.sh
script, so the -devel part is included in the installer.
All header files and import libararies (as created by the
gcc44_build_deps.sh script) are included in the installation
tree in lib/ and include/.
It does not include the sources, and it won't do so in future.
It's supposed to be a binary package, and it also includes the
delevlopment part, to be able to e.g. install octave-forge
packages by using "pkg install foo".
IMO, Its much easier to have the installer optionally perform
gcc44_install_deps.sh then it is to build all the dependencies, which is
really just a big waste of time if you are an end user / developer and
just want to change a few things in the octave source.
Is it really now?
Building octave from source requires you to go through the whole build
process at least once even if you change only a single line of code.
If you view this as a waste of time then I don't really understand
your point.
benjamin