Ron,

I understand. But please understand too that for many years, MINGW is
not xHarbour mainstream compiler, especially for Windows OS. Even the
'build-yourself' binaries from SVN are only available recently. So there
have been almost no reports on MINGW-xHarbour. The same goes through for
Open Watcom and Digital Mars. There has been NIL complaints. It does not
mean that xHarbour + Open Watcom or Digital Mars are OK.

I extend my thanks to Marcos who was willing to post reports.

Andi

On Mon, 23 Jul 2012 13:49:48 -0700
Ron Pinkas <ron.pin...@xharbour.com> wrote:

> Andi,
> 
> Unless someone changed something then no changes are not needed, we 
> supported building Console vs. GUI applications for many years already.
> 
> Ron
> 
> --------------------------------------------------
> From: "Andi Jahja" <andi.ja...@yahoo.co.id>
> Sent: Monday, July 23, 2012 1:38 AM
> To: <xharbour-developers@lists.sourceforge.net>
> Subject: Re: [xHarbour-developers] Error with gtwvt and current xHarbour
> 
> > No. It's not your problem, IMHO.
> > It's a problem with MINGW. I am using version 4.7.1, and still get the
> > same error. Although -mwindows is already there, but is seems that the
> > internal start-up module of MinGW always loads mainstd instead of
> > mainwin. This is strange, because if I use other GUI (ex. FWH), it works
> > OK (MinGW pulled mainwin as startup).
> >
> > I found a work-around then, ie:
> >
> > 1. I delete all the start-ups from VM.LIB, meaning mainstd.o and
> > mainwin.o are no longer in VM.LIB
> >
> > 2. To create application, we have to manually add:
> >
> >  a. mainstd.o for console app
> >  b. mainwin.o for Windows app
> >
> > This is a little bit hassle. If you and other MinGW users do not have
> > objection, then I'll patch the makefiles to reflect this.
> >
> > Andi
> >
> > On Mon, 23 Jul 2012 05:25:22 -0300
> > Marcos Antonio Gambeta <marcosgamb...@yahoo.com.br> wrote:
> >
> >> Em 22/07/2012 23:01, Andi Jahja escreveu:
> >> > Hi Marcos,
> >> >
> >> > Sorry. I read your message too quickly so that I was thinking it is not
> >> > working with BCC, MSVC and MinGW. So, please forget the part of my
> >> > message about BCC and MSVC. Sorry again. :-)
> >> >
> >> > Andi
> >>
> >> No problem. :-)
> >>
> >> I'm using this batch to compile:
> >>
> >> --- buildw.bat ---
> >> set HBPATH=E:\xharbour-rev9590-mingw
> >> set XHBLIBS=-ldebug -lvm -lrtl -lrdd -lmacro -lpp -llang -lcodepage
> >> -lcommon -ldbfntx -ldbfcdx -ldbffpt -lhbsix -lhsx -lgtwin -lgtgui
> >> -lgtwvt -lgtwvw -lpcrepos
> >> set WINLIBS=-luser32 -lwinspool -lole32 -loleaut32 -luuid -lgdi32
> >> -lcomctl32 -lcomdlg32 -lodbc32 -lmapi32 -lws2_32
> >>
> >> :: prg -> c
> >> harbour.exe -n -w -I%HBPATH%\include %1.prg
> >>
> >> :: c -> exe
> >> gcc %1.c -o %1.exe -mwindows -I%HBPATH%\include -L%HBPATH%\lib
> >> -Wl,--start-group %XHBLIBS% %WINLIBS% -Wl,--end-group
> >>
> >> :: clear
> >> del *.c
> >>
> >> set HBPATH=
> >> set HBLIBS=
> >> set WINLIBS=
> >> --- ---
> >>
> >> After I restart my computer, the error message disappeared. But now I
> >> have this behaviour:
> >>
> >> with -mwindows: I can see the program in the task list, but cannot see
> >> the window
> >>
> >> without -mwindows: I can see a console window, but not a GUI window
> >>
> >> My environment is Windows 7 Ultimate 64-bit (first time I develop using
> >> a 64-bit machine) and the GCC version is 4.6.2.
> >>
> >> Maybe something is wrong here. I will revise my environment as soon as
> >> possible.
> >>
> >> Thanks!
> >>


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
xHarbour-developers mailing list
xHarbour-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xharbour-developers

Reply via email to