One other thing.Re-looking at the hbp file. I noticed the #-trace.
That jogged my memory.I have seen quite a few harbour *.c source file file callingsome sort of debug or trace functions. It also seemed if Iremember correctly there wasn't any if it was in the debugmode or not.Because you commented it out it out, you already thoughtof that.Sorry, I'm getting in over my head.Mike
Here's my latest error logbelow -- after making several changes
Mel,FOUND 2 DEBUG.LIB ssssThere is one installed in HB_bc_hwgui 154K 11/8/2007and one installed in HB_bc_oohg 180K 11/6/2008Both are for Borland.Is part of your prg from one of those?
Hello Mel,Your app compiles and links without any errors in Harbour/MinGW environment. I use the following command:hbmk2 t.prg hbct.hbcWhere t.prg is your app.Regards.Ash
Hi Mel,
I just read the whole thread and jump in (late). Maybe I can help.
First of all, (in Windows environment) I recently discovered an astonishing piece of software, LogonView.dll from Microsoft. The nice thing is that the dll can be easily used from inside (x)Harbour. It's a log reader/filter. It's useful to extract data from (nearly) any log/registry you can imagine. I am writig a program to analyze data from Security EventLog and Windows registry. Since I use both Harbour and xHarbour, my code has many lines like:
#IFDEF __XHARBOUR__ etc., but you can also use xhb.lib (a
compatibility lib for Harbour).
If someone is interested I can post the relevant parts. Using
LogonView seems a bit complicated at a first glance (f.e. you must
use a sql syntax to extract data) but after a bit it isn't so
terrible; and anyway this is a good occasion to remember that
(x)Harbour can use any dll exposing COM interface, and this is
TERRIFIC power. I see that there are some new users so maybe just
to remember such a possibility is not inappropriate. :-)
Now the other problem. Yes, Harbour follows a different naming convention for libs. You include xxx and the real name in xHarbour is xxx.lib, in Harbour it is libxxx.lib
I use (in Windows) MINGW with Harbour and BCC 6.9 (the last free version if I am not wrong) with xHarbour, but recently I had to compile Harbour with BCC, to build a lib of mines and to give it to a beta tester (thanks fdaniele) that uses Minigui extended (that uses BCC 5.5).
I was not able to compile all the contribs, but Harbour core compilation went OK, and so went the building of the dBaseWeb library.
So you shouldn't have any problem in compiling a small prog. You
don't need the hbp file for a simple program if the Harbour
environment is rightly configured. Just hbmk2 myprogram.
BTW the line -debug- in the hbp file is probably wrong and must
be removed.
Dan
--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: http://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-users/6889b649-255c-4ac0-8646-81a26d541709%40googlegroups.com.
I believe that Harbour built under Borland can no longer create working apps for me. I just don't have the brainpower to figure out these crazy problems.
then remove that suspicious `-xhb` out of there.I suspect it's the evil switch of the whole story. and then try building again and see whether it helped or not.
--
--
You received this message because you are subscribed to the Google
Groups "Harbour Users" group.
Unsubscribe: harbour-user...@googlegroups.com
Web: http://groups.google.com/group/harbour-users
---
You received this message because you are subscribed to the Google Groups "Harbour Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to harbour-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/harbour-users/12a7de80-befa-4cf3-be59-3b1e58b04150%40googlegroups.com.
I examined the xhb-diffs.txt.