Re: R: R: [GRASS-dev] New Binary Package Project for winGRASS

2008-03-03 Thread Moritz Lennert

On 03/03/08 10:26, [EMAIL PROTECTED] wrote:

Moritz,
 
what release of TCL?


I don't know. I have never tried with anything else but 8.4.

Moritz

 
Marco



*Da:* Moritz Lennert [mailto:[EMAIL PROTECTED]
*Inviato:* dom 02/03/2008 20.47
*A:* [EMAIL PROTECTED]
*Cc:* 'Benjamin Ducke'; 'GRASS Developer Mailing List'
*Oggetto:* Re: R: [GRASS-dev] New Binary Package Project for winGRASS

On 01/03/08 22:14, Marco Pasetti wrote:
 > Hi Benjamin,
 >
 >> Why use ActiveTcl? The regular, GPL'd Tcl compiles without any 
problems and

 > can be distributed freely.
 >
 > Good question! When I planned the work I dind't considered this option,
 > because on the wiki it was (it is) suggested to use ActiveTcl;
 > Probably I should reconsider to build Tcl/Tk from source using MinGW, and
 > then rebuild GRASS...
 >
 > Moritz, what do you think about?

Go ahead for GPL'd tcl/tk.

Moritz



___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


R: R: [GRASS-dev] New Binary Package Project for winGRASS

2008-03-03 Thread marco.pasetti
Moritz,
 
what release of TCL?
 
Marco



Da: Moritz Lennert [mailto:[EMAIL PROTECTED]
Inviato: dom 02/03/2008 20.47
A: [EMAIL PROTECTED]
Cc: 'Benjamin Ducke'; 'GRASS Developer Mailing List'
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS



On 01/03/08 22:14, Marco Pasetti wrote:
> Hi Benjamin,
>
>> Why use ActiveTcl? The regular, GPL'd Tcl compiles without any problems and
> can be distributed freely.
>
> Good question! When I planned the work I dind't considered this option,
> because on the wiki it was (it is) suggested to use ActiveTcl;
> Probably I should reconsider to build Tcl/Tk from source using MinGW, and
> then rebuild GRASS...
>
> Moritz, what do you think about?

Go ahead for GPL'd tcl/tk.

Moritz


___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

R: R: R: [GRASS-dev] New Binary Package Project for winGRASS

2008-03-01 Thread Marco Pasetti
OK

PS: Expat is for XML

Marco 

-Messaggio originale-
Da: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Per conto di Benjamin Ducke
Inviato: sabato 1 marzo 2008 21.40
Cc: 'GRASS Developer Mailing List'
Oggetto: Re: R: R: [GRASS-dev] New Binary Package Project for winGRASS

Marco Pasetti wrote:
> Hi,
> 
>> maybe it would be better, or at least to make note like "this package 
>> is
> required for GRASS compilation", etc.
> 
> Ok. I'll do that later, before to release the final version.
> 
> What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but 
> GDAL uses GEOS, I'm not sure if it uses GSL (even if I think not) and 
> it would

Only QGIS uses GSL for the georeferencer plugin.

> use Expat ...if I could be able to enable that support in GDAL :-)

For what?

> 
> So, summarizing, for the GRASS guide only, should I remove GSL, Expat 
> and GEOS or leave only GEOS?

Only GEOS seems to make sense to me.

Benjamin


> 
> Marco
> 
> -Messaggio originale-
> Da: Martin Landa [mailto:[EMAIL PROTECTED]
> Inviato: sabato 1 marzo 2008 14.44
> A: Marco Pasetti
> Cc: GRASS Developer Mailing List
> Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS
> 
> Hi,
> 
> 2008/3/1, Marco Pasetti <[EMAIL PROTECTED]>:
>>  Related to this (the guide): what do you think about keeping GRASS + 
>> Quantum  GIS building guide together? Actually some things (like 
>> expat, geos and gsl)  are not needed by GRASS, but they are for QGIS.
>> Should I prepare two  different documents, one for GRASS only and one 
>> for both GRASS and QGIS
> 
> maybe it would be better, or at least to make note like "this package 
> is required for GRASS compilation", etc.
> 
> Martin
> 
> --
> Martin Landa  * http://gama.fsv.cvut.cz/~landa 
> *
> 
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
> 
> 

--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel Johanna-Mestorf-Straße 2-6 D 24098
Kiel Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


Re: R: R: [GRASS-dev] New Binary Package Project for winGRASS

2008-03-01 Thread Benjamin Ducke

Marco Pasetti wrote:

Hi,


maybe it would be better, or at least to make note like "this package is

required for GRASS compilation", etc.

Ok. I'll do that later, before to release the final version.

What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but GDAL
uses GEOS, I'm not sure if it uses GSL (even if I think not) and it would


Only QGIS uses GSL for the georeferencer plugin.

use Expat ...if I could be able to enable that support in GDAL :-) 


For what?



So, summarizing, for the GRASS guide only, should I remove GSL, Expat and
GEOS or leave only GEOS?


Only GEOS seems to make sense to me.

Benjamin




Marco

-Messaggio originale-
Da: Martin Landa [mailto:[EMAIL PROTECTED] 
Inviato: sabato 1 marzo 2008 14.44

A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS

Hi,

2008/3/1, Marco Pasetti <[EMAIL PROTECTED]>:
 Related to this (the guide): what do you think about keeping GRASS + 
Quantum  GIS building guide together? Actually some things (like 
expat, geos and gsl)  are not needed by GRASS, but they are for QGIS. 
Should I prepare two  different documents, one for GRASS only and one 
for both GRASS and QGIS


maybe it would be better, or at least to make note like "this package is
required for GRASS compilation", etc.

Martin

--
Martin Landa  * http://gama.fsv.cvut.cz/~landa *

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev




--
Benjamin Ducke, M.A.
Archäoinformatik
(Archaeoinformation Science)
Institut für Ur- und Frühgeschichte
(Inst. of Prehistoric and Historic Archaeology)
Christian-Albrechts-Universität zu Kiel
Johanna-Mestorf-Straße 2-6
D 24098 Kiel
Germany

Tel.: ++49 (0)431 880-3378 / -3379
Fax : ++49 (0)431 880-7300
www.uni-kiel.de/ufg

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev


R: R: [GRASS-dev] New Binary Package Project for winGRASS

2008-03-01 Thread Marco Pasetti
Hi,

>maybe it would be better, or at least to make note like "this package is
required for GRASS compilation", etc.

Ok. I'll do that later, before to release the final version.

What about GEOS, GSL and Expat? Actually, GRASS uses none of them, but GDAL
uses GEOS, I'm not sure if it uses GSL (even if I think not) and it would
use Expat ...if I could be able to enable that support in GDAL :-) 

So, summarizing, for the GRASS guide only, should I remove GSL, Expat and
GEOS or leave only GEOS?

Marco

-Messaggio originale-
Da: Martin Landa [mailto:[EMAIL PROTECTED] 
Inviato: sabato 1 marzo 2008 14.44
A: Marco Pasetti
Cc: GRASS Developer Mailing List
Oggetto: Re: R: [GRASS-dev] New Binary Package Project for winGRASS

Hi,

2008/3/1, Marco Pasetti <[EMAIL PROTECTED]>:
>  Related to this (the guide): what do you think about keeping GRASS + 
> Quantum  GIS building guide together? Actually some things (like 
> expat, geos and gsl)  are not needed by GRASS, but they are for QGIS. 
> Should I prepare two  different documents, one for GRASS only and one 
> for both GRASS and QGIS

maybe it would be better, or at least to make note like "this package is
required for GRASS compilation", etc.

Martin

--
Martin Landa  * http://gama.fsv.cvut.cz/~landa *

___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev