[GRASS-dev] winGRASS Self Installer Package
Gerald Nelson
gnelson at uiuc.edu
Thu Mar 6 09:56:22 EST 2008
Consider adding bc.exe from http://gnuwin32.sourceforge.net/packages.htm.
This is the bash calculator, which appears to work fine when run under msys.
Jerry
---- Original message ----
>Date: Thu, 6 Mar 2008 15:48:05 +0100
>From: <marco.pasetti at alice.it>
>Subject: [GRASS-dev] winGRASS Self Installer Package
>To: "Benjamin Ducke" <benjamin.ducke at ufg.uni-kiel.de>
>Cc: grass-dev at lists.osgeo.org
>
> Hi Benjamin,
>
> I'm afraid, but I cannot find the thread...
> I'm very close to finish the installer; these my
> questions:
>
> 1) name diplayed in the installer: GRASS 6.3.0RC5 or
> GRASS 6.3.0RC5 for Windows or simply GRASS 6.3?
>
> 2) MSYS files: I decided to include the whole MSYS
> env, excluding MinGW, obvioulsy; list follows:
> basename.exe
> cut.exe
> false.exe
> id.exe
> ls.exe
> mv.exe
> sed.exe
> tar.exe
> uniq.exe
> bzip2.exe
> date.exe
> find.exe
> info.exe
> m4.exe
> od.exe
> sh.exe
> tee.exe
> vim.exe
> cat.exe
> diff.exe
> fold.exe
> infokey.exe
> make.exe
> patch.exe
> sleep.exe
> texindex.exe
> wc.exe
> chmod.exe
> diff3.exe
> gawk.exe
> install-info.exe
> makeinfo.exe
> ps.exe
> sort.exe
> touch.exe
> xargs.exe
> cmp.exe
> dirname.exe
> grep.exe
> install.exe
> md5sum.exe
> rm.exe
> split.exe
> tr.exe
> comm.exe
> env.exe
> gzip.exe
> less.exe
> mkdir.exe
> rmdir.exe
> stty.exe
> true.exe
> cp.exe
> expr.exe
> head.exe
> ln.exe
> mount.exe
> rxvt.exe
> tail.exe
> uname.exe
>
> what to keep, what to remove?
> 3) bin executables: there are actually some usefull
> apps to add; thi is the list of my /bin exes (I
> built a brand new msys env with grass only needed
> libs):
>
> XMLTester.exe
> flex.exe
> gdalmanage.exe
> invgeod.exe
> ogrtindex.exe
> tiff2bw.exe
> tiffinfo.exe
> bison.exe
> gdal_contour.exe
> gdaltindex.exe
> invproj.exe
> pal2rgb.exe
> tiff2pdf.exe
> tiffmedian.exe
> bmp2tiff.exe
> gdal_grid.exe
> gdaltransform.exe
> m4.exe
> ppm2tiff.exe
> tiff2ps.exe
> tiffset.exe
> cs2cs.exe
> gdal_rasterize.exe
> gdalwarp.exe
> nad2bin.exe
> proj.exe
> tiff2rgba.exe
> tiffsplit.exe
> fax2ps.exe
> gdal_translate.exe
> geod.exe
> nad2nad.exe
> ras2tiff.exe
> tiffcmp.exe
> fax2tiff.exe
> gdaladdo.exe
> gif2tiff.exe
> nearblack.exe
> raw2tiff.exe
> tiffcp.exe
> fftw-wisdom.exe
> gdalenhance.exe
> gsl-histogram.exe
> ogr2ogr.exe
> rgb2ycbcr.exe
> tiffdither.exe
> flex++.exe
> gdalinfo.exe
> gsl-randist.exe
> ogrinfo.exe
> thumbnail.exe
> tiffdump.exe
>
> what to keep, what to remove?
>
> Thanks
>
> Marco
>
>
> ------------------------------------------------
>
> Da: grass-dev-bounces at lists.osgeo.org per conto di
> Benjamin Ducke
> Inviato: gio 06/03/2008 15.15
> Cc: grass-dev at lists.osgeo.org
> Oggetto: Re: [GRASS-dev] winGRASS Self Installer
> Package
>
> I remember dimly that we discussed these things
> before, a few
> weeks back when I was trying to put together a new
> WinGRASS
> distribution. I think that Glynn posted a list of
> useful tools for
> inclusion to this mailing list, back then.
>
> There are other useful things, such as wget, curl,
> tar, unzip, awk,
> sed, ...
> Some of them may be needed by shell scripts.
>
> Maybe it would be a good idea to put up a Wikipage
> and start
> adding these things to it?
>
> Benjamin
>
> Paul Kelly wrote:
> > On Thu, 6 Mar 2008 marco.pasetti at alice.it wrote:
> >
> >> Hi,
> >>
> >>> First of all, I want to express my thanks on
> behalf of students here
> >>> who are using GRASS on Windows [...]
> >>
> >> you're welcome... did you already read my new
> GRASS Windows Native
> >> Binary Building Guide?
> >>
> http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html
> >>
> <http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html>
> >> I'm updating it with packaging instructions
> >> when I'll have enough free time I'll put it into
> GRASS trac
> >>
> >>> My suggestion is that you include SQLite but not
> PostgreSQL.[...]
> >>
> >> Do you think that libsqlite3-0.dll is enough? in
> my (built) sqlite
> >> directory I have /bin with 1 dll and 1 exe,
> /include with only
> >> includes and /lib dir with static libs.
> >
> > If you've compiled GRASS against the .dll then you
> don't need the static
> > libraries. If you've compiled GRASS against the
> static libraries then
> > you don't need to include anything - the required
> libraries will be
> > statically linked into the GRASS modules (you can
> usually tell this if
> > the size of the binaries is very large. I usually
> delete the static
> > libraries after compiling to make sure they are
> not picked up by
> > accident). You certainly don't need to include the
> header files in
> > include/ for a binary distribution - they are only
> necessary for
> > compiling. If there are some useful utility
> programs in bin/ they may be
> > worth sticking into the GRASS bin directory too,
> e.g. gdalwarp.exe and
> > gdalinfo.exe from GDAL and cs2cs.exe and
> nad2bin.exe from PROJ.
> >
> > For a lot of packages though you just need the DLL
> and can stick it
> > straight into the GRASS $GISBASE/lib directory
> before packaging up the
> > binary distribution.
> >
> > Paul
> > _______________________________________________
> > grass-dev mailing list
> > grass-dev at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev
> >
> >
>
> --
> Benjamin Ducke
> Senior Applications Support and Development Officer
>
> Oxford Archaeological Unit Limited
> Janus House
> Osney Mead
> OX2 0ES
> Oxford, U.K.
>
> Tel.: ++44 (0)1865 263 800
> benjamin.ducke at oxfordarch.co.uk
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>________________
>_______________________________________________
>grass-dev mailing list
>grass-dev at lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/grass-dev
Gerald Nelson
Professor, Dept. of Agricultural and Consumer Economics
University of Illinois, Urbana-Champaign
office: 217-333-6465
cell: 217-390-7888
315 Mumford Hall
1301 W. Gregory
Urbana, IL 61801
More information about the grass-dev
mailing list