extern library in Unix

[Mufasa2]

My problem is the following:

I have a C++ program in a WinXP machine. This program has to call some functions from a extern library which only works in a Silicon machine (OS UNIX). So somehow i have to say to my C++ program to look for the library functions in another computer...

I have an example where this connection is made (maybe it helps):

Its a program example which runs in the windows machine which uses functions of the extern library. This program, when compiled, generates an executable.
Before running the .exe, a .bat file must be run. This .bat file sets up a environement variable "CONTROL" like this:

set CONTROL=c:\users\......\definition\sites

In this "sites" file, the IP number of the computer where the library is (the UNIX computer) is referenced. So thats how the connection with the two machines is made.

Afterwards, u run the .exe and you can make use of the extern library.

However, in my case, i dont generate any executable. The functions of the extern library must be called "directly" by my program. But it never compiles because it keeps saying "LINK ERROR: extern symbol XXXX not solved" (XXXX is every function of the extern library)

Can u help me on this? I would really appreciate it since it is basic for my end-of-studies projet

I work with Visual C++. The two computers work in LAN.

I dont know if i was any clear... im not very familiar with informatics.

Thanks in advance

 

[Salem]

> But it never compiles because it keeps saying "LINK ERROR: extern symbol XXXX not solved"
You can't just point at a function on another machine and say "call it".

Do a google search for "remote procedure call". This is only really worth doing if the called function does a subtantial amount of work, because of the overheads in sending network message traffic between the machines.

--

 

[Cagliostro]

Yes, RPC as well as some RPC based tehnologies CORBA and DCE-RPC. You also could choose some a bit simplier ways to communicate. For example TCP sockets and/or any TCP based protocols.

Ion Filipski