[GRASS-dev] wingrass640

Hi,

I am currently trying to compile GRASS (releasebranch_6_4) under MS
Windows [1].

TODO:

* compile with regex
* compile wxGUI digitizer

* and optionally compile wxGUI Nviz extension

wxGUI seesm to work (add raster and vector layer, render map).

It would be also good to modify Windows installer: add to the menu
(and desktop) two items

* TCLTK GRASS
* WX GRASS

for easy testing new wxGUI interface under MS Windows.

Martin

[1] http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#GRASS

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

I also had to add a compile regex from src for configure to work. I
also updated various other dependencies and msys/mingw itself since I
got a missing "bcopy" error. That is fixed now but I think the
difference in updates between when I first ran configure and make on
the grass64 source and now is causing problems.

I get the following error:

make[2]: *** No rule to make target
`/usr/local/src/grass-6.4.0/dist.i686-pc-mingw32/lib/libgrass_vect.dll',
needed by `/usr/local/src/grass-6.4.0/dist.i686-pc-mingw32/bin/v.sample.exe'.
Stop.
make[2]: Leaving directory `/usr/local/src/grass-6.4.0/vector/v.sample'

This is just an example, I get it for every module as far as I can tell.

I re-ran configure after all my updates, also I tried 'make clean'
before running make again but no luck so far.

-Colin

On Sun, Dec 21, 2008 at 8:35 AM, Martin Landa <landa.martin@gmail.com> wrote:

Hi,

I am currently trying to compile GRASS (releasebranch_6_4) under MS
Windows [1].

TODO:

* compile with regex
* compile wxGUI digitizer

* and optionally compile wxGUI Nviz extension

wxGUI seesm to work (add raster and vector layer, render map).

It would be also good to modify Windows installer: add to the menu
(and desktop) two items

* TCLTK GRASS
* WX GRASS

for easy testing new wxGUI interface under MS Windows.

Martin

[1] http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#GRASS

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Colin Nielsen wrote:

I also had to add a compile regex from src for configure to work. I
also updated various other dependencies and msys/mingw itself since I
got a missing "bcopy" error. That is fixed now but I think the
difference in updates between when I first ran configure and make on
the grass64 source and now is causing problems.

I get the following error:

make[2]: *** No rule to make target
`/usr/local/src/grass-6.4.0/dist.i686-pc-mingw32/lib/libgrass_vect.dll',

This means that vector library failed to compile. Do you get an error
from:

  make -C lib/vector
?

--
Glynn Clements <glynn@gclements.plus.com>

On Sun, 21 Dec 2008, Martin Landa wrote:

Hi,

I am currently trying to compile GRASS (releasebranch_6_4) under MS
Windows [1].

TODO:

* compile with regex

I can report it works fine with the Gnuwin32 regex packages. Another issue is that Cairo support in the 6.4 configure script requires the pkg-config command which isn't generally available on Windows. But the 7.0 configure script doesn't require pkg-config and in any case Cairo support isn't particularly important for 6.4 so I don't think this needs to be addressed.

It would be also good to modify Windows installer: add to the menu
(and desktop) two items

* TCLTK GRASS
* WX GRASS

Something else that might be worth investigating would be to implement an option to select the language. I've found that it can easily be done by setting the environment variable LC_ALL to the country code (if compiled with NLS support - Gnuwin32 intl packages work fine here) but the average Windows user may not know how to set an environment variable and I wonder is there some standard way applications using NLS support on Windows set the language.

Paul

Paul Kelly wrote:

> It would be also good to modify Windows installer: add to the menu
> (and desktop) two items
>
> * TCLTK GRASS
> * WX GRASS

Something else that might be worth investigating would be to implement an
option to select the language. I've found that it can easily be done by
setting the environment variable LC_ALL to the country code (if compiled
with NLS support - Gnuwin32 intl packages work fine here) but the average
Windows user may not know how to set an environment variable and I wonder
is there some standard way applications using NLS support on Windows set
the language.

Native Windows programs normally get translated messages from string
table resources in the binary.

Windows understands setlocale(LC_ALL, "") etc to use the system
locale, as set from the control panel rather than environment
variables.

But Windows doesn't have LC_MESSAGES, and we certainly shouldn't be
calling setlocale(LC_ALL, ""), as that will change LC_NUMERIC, which
affects printf("%f").

AFAICT, the GnuWin32 libintl/gettext requires manual configuration;
the generic installation and usage instructions say:

  http://gnuwin32.sourceforge.net/install.html

  Most GNU packages have the ability to output messages in
  several languages. This native-language support (NLS) requires
  the LibIntl and the LibIconv libraries. On MS-Windows they
  have been adapted so that NLS chooses the system language,
  unless the environment variables LANG and LANGUAGE has been
  set. The language codes (ISO 639) for these environment
  variables are different from the MS-Windows ones. When using a
  program in a console window (command.com or cmd.exe) and
  setting LANG and LANGUAGE, you must also set the correct code
  page with the chcp command; for Western European languages,
  code page 1252 usually suffices. For other languages, such as
  those with a Cyrillic character set, NLS may not operate
  correctly. If you want to disable NLS, then set the
  environment variables LANGUAGE and LANG to en; then all
  messages will be in English.

It's easy enough to get Windows' version of the current locale, with
e.g.:

  orig_locale = setlocale(LC_CTYPE, NULL);
  setlocale(LC_CTYPE, "");
  default_locale = setlocale(LC_CTYPE, NULL);
  setlocale(LC_CTYPE, orig_locale);

However, that will be a string such as "English_United Kingdom.1252".

If you want the ISO-639 code, you can use GetUserDefaultLCID() to get
an ID, then copy the windows_locale table from Python's locale.py
module to convert it.

--
Glynn Clements <glynn@gclements.plus.com>

Hi,

2008/12/21 Martin Landa <landa.martin@gmail.com>:

I am currently trying to compile GRASS (releasebranch_6_4) under MS
Windows [1].

TODO:

* compile with regex
* compile wxGUI digitizer

* and optionally compile wxGUI Nviz extension

wxGUI seesm to work (add raster and vector layer, render map).

It would be also good to modify Windows installer: add to the menu
(and desktop) two items

* TCLTK GRASS
* WX GRASS

for easy testing new wxGUI interface under MS Windows.

is there someone (Marco?) who is going to prepare Windows installer
for RC1 with wxGUI support (propably except of vector digitizer and
Nviz extension)?

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

Hi all,

is there someone (Marco?) who is going to prepare Windows installer
for RC1 with wxGUI support (propably except of vector digitizer and
Nviz extension)?

I'm just back in office. I'm 455 mails late... but I'll start to work on the
new GRASS build right now.

The "blocking" thing is related to the "building environment update" I
planned; in fact, some problems in the GRASS building are generated by some
MSYS/MinGW lacks... that's why I decided to replace my current MSYS
installation with a fully updated one... and here that's the problem! the
MSYS project is poorely documented, and the 1.0.11 version of the istaller,
even if available on the repository, is not officially present in the
project list... but it seems to be more recent (and bug fixer) than the
currently proposed one... even if not fully updated! and the updated are a
little be confused (in the way you cannot just unpack the new files because
some updates overwrite each other creating messy and buggy installations).

I've been reading some articles and mails and I'm figuring how to solve this
messy situation...

I think I can give you a precise dead-line in about one or two days.
I'm sorry, but I also have my regular work here :wink: ...
I'll do as best as I can.

Regards... and happy new year :slight_smile:

-------------------------------------------------------------------------
Ing. Marco Pasetti
Università degli Studi di Brescia
Facoltà di Ingegneria
Dipartimento di Ingegneria Meccanica e Industriale
Via Branze, 38 - 25123 Brescia - Italy
Phone: (+39) 030 371 54 97
Mobile: (+39) 328 56 12 639
Skype: marco.pst
-------------------------------------------------------------------------

hi Marco,

On Wed, Jan 7, 2009 at 2:18 PM, Marco Pasetti <pasetti.marco@gmail.com> wrote:
...

The "blocking" thing is related to the "building environment update" I
planned; in fact, some problems in the GRASS building are generated by some
MSYS/MinGW lacks... that's why I decided to replace my current MSYS
installation with a fully updated one... and here that's the problem! the
MSYS project is poorely documented, and the 1.0.11 version of the istaller,
even if available on the repository, is not officially present in the
project list... but it seems to be more recent (and bug fixer) than the
currently proposed one... even if not fully updated! and the updated are a
little be confused (in the way you cannot just unpack the new files because
some updates overwrite each other creating messy and buggy installations).

I've been reading some articles and mails and I'm figuring how to solve this
messy situation...

may I suggest to move the build instructions into the Wiki? Currently we have

http://grass.osgeo.org/grass63/binary/mswindows/native/#Build GRASS From Source
http://trac.osgeo.org/grass/wiki/BuildingOnWindows
http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#GRASS

which is rather confusing. A publicly editable document may accelerate the
progress to obtain a winGRASS 6.4.0RC2 since more people can add
suggestions and update the document to GRASS 6.4.x.

Markus

Hi Markus,

may I suggest to move the build instructions into the Wiki? Currently we

have

http://grass.osgeo.org/grass63/binary/mswindows/native/#Build GRASS
From Source
http://trac.osgeo.org/grass/wiki/BuildingOnWindows
http://www.webalice.it/marco.pasetti/grass/BuildFromSource.html#GRASS

which is rather confusing. A publicly editable document may accelerate the
progress to obtain a winGRASS 6.4.0RC2 since more people can add
suggestions and update the document to GRASS 6.4.x.

OK. I'll consider that.
Regards,

Marco