> It's unrelated to recent changes. If you check ChangeLog
> and/or SVN history, this error msg has been placed there long
> time ago. GTWVW code doesn't comply with most of Harbour
> rules that normally ensure portability between C compilers and
> CPUs, so f.e. it doesn't work with x86_64. It also doesn't support
> C++, it generates thousands of warnings so these need to be
> suppressed also. Recently it also fell behind of UTF8 HVM support.

> -- Viktor

> On Sat, Jun 2, 2012 at 6:19 PM, Rossine <qii...@ig.com.br> wrote:
> > Hello Massimo,

> > Many thank´s for this explanation,

> > Rossine.

> > On 2 jun, 12:12, Massimo Belgrano <mbelgr...@deltain.it> wrote:
> >> afaik not work after recent evolution unicode in hvm from   Przemek.
> >>  This is basic version which introduce to HVM CPs with custom encodings.
> >>     Some contrib code has to be updated to work correctly with it.
> >>     I hope that developers interesting in will make necessary updates.
> >>     I haven't touched GTWVW code at all - sorry but it needs very serious
> >>     work to make it production ready and fix all existing problems.
> >> so i suggest evolve your application to gtwvg ready and reliable but not
> >> 100% compatible
> >> same #include maj facilitate you the porting

> >> 2012/6/2 Rossine <qii...@ig.com.br>

> >> > Hi,

> >> > When trying to generate gtwvw to 64 bits, hbmk2 informed me that it
> >> > only works on 32 bits. How it would work on 64 bits too ?

> >> > c:\harbour\examples\gtwvw>hbmk2 gtwvw.hbp
> >> > hbmk2: Processando opções do ambiente: -compiler=mingw64
> >> > Skipped: 'gtwvw' only supported on win x86 platform.

> >> > Best regards,

> >> > Rossine.

> >> --
> >> Massimo Belgrano

> --
> Viktor