comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: IDL make_dll and unresolved externals
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL make_dll and unresolved externals [message #69690 is a reply to message #69686] Tue, 02 February 2010 18:13 Go to previous messageGo to previous message
james is currently offline  james
Messages: 9
Registered: March 1992
Junior Member
I think my problem currently is with make_dll, and not with
call_external. After make_dll is called, I have an unresolved
external error at compile time.
I do set the header directories and .lib file locations parameters for
the make_dll command, though. As for finding the opencv dll's, I'm
not sure how to direct its location using the make_dll command. Is
there somewhere I can set this on the IDL workbench?

I am unfamiliar with dependency walker and idl_opserver. I will look
into these. (I am relatively new to IDL)


Wox wrote:
> On Sat, 30 Jan 2010 19:03:59 -0800 (PST), james
> <james5452003@yahoo.com> wrote:
>
>> Hi,
>> I am trying to use the call_external for C code and am using make_dll
>> to compile the dll. The problem I am having is with the make_dll. I
>> am including another library (opencv) in the c code and it seems to
>> compile okay when I just declare a (opencv type) variable from that
>> library. But when I include a call of any one of the functions from
>> the (opencv) library in the code, there is unresolved external
>> compiler error on it.
>>
>> Any suggestions on what I am doing incorrectly? Can other libraries
>> like opencv be used for IDL?
>
> Ok, just to make sure I understand: you make a dll with export
> functions in portable calling convention. In one of these functions
> you call a function from the opencv library. Using call_external gives
> some kind of error which you expect comes from calling the opencv
> function.
>
> Did you link opencv statically or dynamically (check with depency
> walker). If it's dynamic linking, make sure your dll is finding the
> opencv dll.
>
> Did you try calling your dll from C? Did is work?
>
> You can also attach a debugger to idl_opserver and set a breakpoint
> just before the error occurs. Easy in visual studio express (free),
> not sure what you have...
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Re: Simple question about the '>' sign.
Next Topic: Extract / interpolate in 3d atmospheric field

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 05:05:13 PDT 2025

Total time taken to generate the page: 1.04037 seconds