I think that QGIS shloud use GRASS stable release, but I am not
sure if there are some important fixes missing in the last stable 6.2.1.
For now stick with HEAD (currently 6.3.-cvs) where the patch was applied
(it should become future stable 6.4.0) I asked also to apply the patch
in 6.2 branch (it will be in the next stable 6.2.2).
Please close the ticket once you update GRASS from CVS in msys.tar.bz2.
Still there is the problem with (sometimes, according how qgis was compiled
and started) flashing console when GRASS db driver is started.
Anybody knows how to suppress console on Windows for a program
run by spawnl() which must be started with stdin/stdout?
Radim
On 12/18/06, Tim Sutton <tim@linfiniti.com> wrote:
Hi
Yes - unless you are happy to use grass cvs head for the qgis release
and the patch is already in grass? If you want to use latest stable
only, I will update the msys.tar.bz2 file to the tagged grass stable
release and then apply the patch in the generally downloadable msys
tarball....?
Regards
Tim
On 12/17/06, Radim Blazek <radim.blazek@gmail.com> wrote:
> I have fixed https://svn.qgis.org/trac/ticket/448
> but the patch must be applied to GRASS. So I left it open
> until the GRASS which will be used to build official QGIS binaries
> for windows is patched.
>
> We should let people know that this patch must be applied.
> Where should I add a warning? In README_windows.txt?
>
> Radim
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer@lists.qgis.org
> http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-developer
>
--
Tim Sutton
Visit http://qgis.org for a great Open Source GIS
Home Page: http://linfiniti.com
Skype: timlinux
MSN: tim_bdworld@msn.com
Yahoo: tim_bdworld@yahoo.com
Jabber: timlinux
Irc: timlinux on QGIS at freenode.net
In the GRASS stable release tons of Windows fixes are
missing and it's rather impossible to backport them
(only if you have much time).
I have now merged the patch into GRASS 6.2 stable release as
well.
BTW: Radim, you have CVS write access, feel free to fix
directly.
Markus
On Mon, Dec 18, 2006 at 10:51:02AM +0100, Radim Blazek wrote:
I think that QGIS shloud use GRASS stable release, but I am not
sure if there are some important fixes missing in the last stable 6.2.1.
For now stick with HEAD (currently 6.3.-cvs) where the patch was applied
(it should become future stable 6.4.0) I asked also to apply the patch
in 6.2 branch (it will be in the next stable 6.2.2).
Please close the ticket once you update GRASS from CVS in msys.tar.bz2.
Still there is the problem with (sometimes, according how qgis was compiled
and started) flashing console when GRASS db driver is started.
Anybody knows how to suppress console on Windows for a program
run by spawnl() which must be started with stdin/stdout?
Radim
On 12/18/06, Tim Sutton <tim@linfiniti.com> wrote:
>Hi
>
>Yes - unless you are happy to use grass cvs head for the qgis release
>and the patch is already in grass? If you want to use latest stable
>only, I will update the msys.tar.bz2 file to the tagged grass stable
>release and then apply the patch in the generally downloadable msys
>tarball....?
>
>Regards
>
>Tim
>
>On 12/17/06, Radim Blazek <radim.blazek@gmail.com> wrote:
>> I have fixed https://svn.qgis.org/trac/ticket/448
>> but the patch must be applied to GRASS. So I left it open
>> until the GRASS which will be used to build official QGIS binaries
>> for windows is patched.
>>
>> We should let people know that this patch must be applied.
>> Where should I add a warning? In README_windows.txt?
>>
>> Radim
>> _______________________________________________
>> Qgis-developer mailing list
>> Qgis-developer@lists.qgis.org
>> http://lists.qgis.org/cgi-bin/mailman/listinfo/qgis-developer
>>
>
>
>--
>--
>Tim Sutton
>
>Visit http://qgis.org for a great Open Source GIS
>Home Page: http://linfiniti.com
>Skype: timlinux
>MSN: tim_bdworld@msn.com
>Yahoo: tim_bdworld@yahoo.com
>Jabber: timlinux
>Irc: timlinux on QGIS at freenode.net
>
--
Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy
In the GRASS stable release tons of Windows fixes are
missing and it's rather impossible to backport them
(only if you have much time).
IMO they are too many and too deep to backport without harming the
branch's stability. Windows support is, in fact, still under active
development. And these could perhaps be better termed "Windows
accommodations" instead of "Windows fixes".
So the question is, for QGIS 0.8 pacakges where the GRASS startup, GUI,
wrapper scripts, build system, etc., code doesn't matter:
6.2-CVS (with Radim's patch)
or (very similar)
6.2.1.qgis.custom (6.2.1 with Radim's patch)
or
6.3-CVS (tagged as 6.3.0 just before qgis 0.8 is released)
?
to consider:
QGIS will be released to a wide audience of Windows users with no GRASS
experience. If what they get from the GRASS plugin is broken alpha-ware,
this will [mistakenly] harm GRASS's reputation as a stable product and
a viable alternative to entrenched softwares.
I think that QGIS shloud use GRASS stable release, but I am not
sure if there are some important fixes missing in the last stable
6.2.1.
AFAICT (others who did the work can better answer), I think most of the
6.3-cvs changes have had to do with the GUI, build system, etc, and not
the modules and libraries (which is what qgis is concerned with).
There have probably been a few system("ls %s"); system("rm %s"); type
portability fixes in the modules/libs to watch out for though.
So maybe 6.2.1+Radim's patch is ok to use as the basis for the 0.8 grass
plugin after all??
I have not been following GRASS development for a while.
According to what Hamish wrote, there should be no fixes important
for QGIS in 6.3. I dont know exactly when releasebranch_6_2 was created
but it seems that in 28 August 2006. IIRC I sent some fixes after this date
but I am not sure. Both 6.3 and 6.2.1 have bugs but the problem
of 6.3 is that it is changing every day. It will be probably better to
use the stable release 6.2.1 + the last patch for start.c.
Maybe it will be necessary to add some other important patches,
maybe not. In fact, we have to create our stable version of GRASS
for QGIS/Win from 6.2.1.
Maybe it would be better to create a branch for it in CVS?
Or just a dir with patches in QGIS SVN?
Radim
On 12/19/06, Tim Sutton <tim@linfiniti.com> wrote:
Hi
I really have no expertise on this, so I look to your guidance on the
final decision...Its stll not clear to me from this discussion what
the concensus is.
Regards
Tim
On 12/19/06, Hamish <hamish_nospam@yahoo.com> wrote:
> Radim Blazek wrote:
> > I think that QGIS shloud use GRASS stable release, but I am not
> > sure if there are some important fixes missing in the last stable
> > 6.2.1.
>
> AFAICT (others who did the work can better answer), I think most of the
> 6.3-cvs changes have had to do with the GUI, build system, etc, and not
> the modules and libraries (which is what qgis is concerned with).
>
> There have probably been a few system("ls %s"); system("rm %s"); type
> portability fixes in the modules/libs to watch out for though.
>
> So maybe 6.2.1+Radim's patch is ok to use as the basis for the 0.8 grass
> plugin after all??
>
> Hamish
>
--
Tim Sutton
Visit http://qgis.org for a great Open Source GIS
Home Page: http://linfiniti.com
Skype: timlinux
MSN: tim_bdworld@msn.com
Yahoo: tim_bdworld@yahoo.com
Jabber: timlinux
Irc: timlinux on QGIS at freenode.net