New user, help with unresolved externals

I am new to xHarbor. I am not new to Clipper. I hav an older
application I am wanting to compile with xHarbour. I am trying it via
the demo at xHarbour.com using xHarbour Builder. I believe I have
everthing setup properly, or close.

When I choose build, I get a reasonably short list of unresolved
symbols. At least the majority appear to be from functions I used out
of the Nanforum library, and from the Clipper Tools library. For
example:

_HB_FUN_FT_MKDIR
_HB_FUN_FT_FLOPTST
_HB_FUN_SWPRUNCMD
_HB_FUN_MIL2CIV

_HB_FUN_COM_OPEN
_HB_FUN_COM_INIT
_HB_FUN_COM_SEND
_HB_FUN_COM_CLOSE
_HB_FUN_COM_RTS

I was under the impression xHarbour was 100% compatible wht these so
hopefully I am just doing something wrong, or missing doing something.

Can anyone get me pointed in teh right direction to resolve these in
general? If I have to develop workarounds for some of them I
understand, but surely some will work?

Thanks,
Scott

OK, I found if I added nanfor.lib from the xHB dist to the 3rd tab of
xBuilder's lib list, I got most of the FT_ functions resolved. Happy
with that, I tried adding CT3 and CT3COMM lib files, but that does nto
help. I am down to these:

* A couple misc functions
FT_FLOPTST <- floppy test
FT_FLASTRE <- last record in text file

*all the clipper tools comm functions I use
COM_OPEN
COM_INIT
COM_SEND
COM_CLOSE
COM_RTS
* these are BIG ones to me. These must work. Or a anternative.

* I forget, but think these ca from Blinker:
SWPRUNCMD
SWPERRLEV
* I used these to swap out so I could zip a file. I would not be
surprised to not see these supported in wndows, I can probably work
around them with the new available zip functions.


Anyone help, particularly withthe COM_x functions?

Thanks,
Scott

Shorton

com functions on xharbour builder are in ct3comm.lib
alternatives for this functions are the xhbcomm lib, but you need to rewrite
the com functions call

Regards
Luiz

Dear SHORTON:

"SHORTON" <sales07@techht.com> wrote in message
news:dc51b41c-f229-42e1-be1e-e2a8b8ebacf1@y21g2000hsf.googlegroups.com...
....
> Anyone help, particularly withthe COM_x functions?

The commerical packages just above entry level have those
functions in them. For the free version, search this newsgroup
for mentions of "hbcomm.lib".

David A. Smith

> * I forget, but think these ca from Blinker:
> SWPRUNCMD
> SWPERRLEV
> * I used these to swap out so I could zip a file. I would not be
> surprised to not see these supported in wndows, I can probably work
> around them with the new available zip functions.

I've posted sources for these functions on this NG - please search the NG.

Ron

On Apr 12, 4:15*pm, "luiz Rafael Culik Guimaraes"
<l...@xharbour.com.br> wrote:
> Shorton
>
> com functions on xharbour builder are in ct3comm.lib
> alternatives for this functions are the xhbcomm lib, but you need to rewrite
> the com functions call
>
> Regards
> Luiz

Luiz, David:

Thank you for the pointers and help. I did try the ct2comm.lib in the
demo version, but I still get the unresolved externals. Is that lib
somehow crippled in the demo version?

FWIW, I have every intention of purchasing the commercial version, but
I wanted to see what an app looks like compiled with xHarbour before
spending the $400+docs to help out. I can go comment out those calls
I suppose but then I can't test the app.

I'd prefer not to rewrite it twice, once for the free version, once
for commercial. I wante to verify it is not supposed to work inteh
demo version before I proceed any rewriting.

I did search for the free version as suggested, but I wasnt' sure if I
found it or not. I definately did not find a .lib file, I'm not sure
if the code I found was "it" or not. Luiz, you are the maintiner?
Can you point me to the software? Being brand new to this, I'm a
little fuzzy on exactly what I'm looking for.

Thanks again! Scott

On Apr 12, 6:23*pm, "Ron Pinkas" <R...@xHarbour.com> wrote:
> > * I forget, but think these ca from Blinker:
> > SWPRUNCMD
> > SWPERRLEV
> > * I used these to swap out so I could zip a file. *I would not be
> > surprised to not see these supported in wndows, I can probably work
> > around them with the new available zip functions.
>
> I've posted sources for these functions on this NG - please search the NG.
>
> Ron

Ron, thank you. I saw something you posted that said it was
untested. It looked like "regular" .prg code. I'm not used to the
power of xHarbour, so that seemed too easy (to use). If that was it,
would I simply put that "prg looking" code in a prg and compile with
it?

Best,
Scott

Scott,

<<<
Ron, thank you. I saw something you posted that said it was
untested. It looked like "regular" .prg code. I'm not used to the
power of xHarbour, so that seemed too easy (to use). If that was it,
would I simply put that "prg looking" code in a prg and compile with
it?
>>>

Yes, it's normal PRG code, which you can simply add to one of your sources.

Ron

Scott,

<<<
Ron, thank you. I saw something you posted that said it was
untested. It looked like "regular" .prg code. I'm not used to the
power of xHarbour, so that seemed too easy (to use). If that was it,
would I simply put that "prg looking" code in a prg and compile with
it?
>>>

Yes, it's normal PRG code, which you can simply add to one of your sources.

Ron