For Programmers: Free Programming Magazines  


Home > Archive > Clarion > November 2005 > Problem linking after converting from 5.5 to 6.2









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Problem linking after converting from 5.5 to 6.2
HarleyMan

2005-11-08, 6:55 pm

Hi All: I've just upgraded from CLW 5.5 to 6.2 and have run into my
first problem. I've been working with Clarion for year (back to the
old DOS days) and most of my applications are hand coded. I have a
library of about 20 service routines. My problem is with these service
modules. Most of them are small Clarion routines that use MESSAGE() to
interface with a user, though three of the routines use a WINDOW to
interface. It's these three routines that are causing the problem.
All routines compile clean (I've used most of them without making any
changes since early version of CLW) but when I try to link them I get
the following errors:

Unresolved External Cla$Hooksstring in HlpAbout.obj
Unresolved External Cla$Hookstring in HlpAbout.obj
Unresolved External Cla$Hookimage in HlpAbout.obj
Unresolved External Cla$Hookentry in HlpAbout.obj
Unresolved External Cla$Hookbutton in HlpAbout.obj
Unresolved External Cla$Hookprompt in HlpAbout.obj

This is for only one of the three modules..... To try and resolve the
problem I copied the source code into the program I was trying to link
the module too and everything compiles, links and runs clean. So it
looks like a link problem. Any ideas????

Thanks - Stan

HarleyMan

2005-11-08, 6:55 pm


HarleyMan wrote:
> Hi All: I've just upgraded from CLW 5.5 to 6.2 and have run into my
> first problem. I've been working with Clarion for year (back to the
> old DOS days) and most of my applications are hand coded. I have a
> library of about 20 service routines. My problem is with these service
> modules. Most of them are small Clarion routines that use MESSAGE() to
> interface with a user, though three of the routines use a WINDOW to
> interface. It's these three routines that are causing the problem.
> All routines compile clean (I've used most of them without making any
> changes since early version of CLW) but when I try to link them I get
> the following errors:
>
> Unresolved External Cla$Hooksstring in HlpAbout.obj
> Unresolved External Cla$Hookstring in HlpAbout.obj
> Unresolved External Cla$Hookimage in HlpAbout.obj
> Unresolved External Cla$Hookentry in HlpAbout.obj
> Unresolved External Cla$Hookbutton in HlpAbout.obj
> Unresolved External Cla$Hookprompt in HlpAbout.obj
>
> This is for only one of the three modules..... To try and resolve the
> problem I copied the source code into the program I was trying to link
> the module too and everything compiles, links and runs clean. So it
> looks like a link problem. Any ideas????
>
> Thanks - Stan


With the help of someone at TopSpeed the problem was found - the
routines were compiled with a run-time lib type of local while the main
pgm was compiled with run-time lib of Standalone.... hope this helps
others....

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com