BOCCARA Michael (MICHAEL.BOCCARA++at++siege.aerospatiale.fr)
Tue, 30 Sep 1997 14:20:03 +0200
I just made something today for combining Rapidapp-generated Vk code with my
Performer program, without all the stuff required in the motif.c example.`
Step 1:
change the main.C generated file into vkmain.C
Step 2:
into vkmain.C, change int main(argc, argv) into vkmain(argc, argv)
Step 3:
insert vkmain.o and all the Rapidapp C file names into your makefile,
including the vk lib links, etc.
Step 4:
in the Performer code, just before entering the main loop (with pfFrame),
call a fork :
extern vkmain(...
vk_pid = fork();
if(vk_pid < 0)
...fork failed
else if(!vk_pid)
vkmain(argc, argv)
while(!exit)
pfSync()
pfFrame()
.... etc.
And it works !!!
I just toggled stats using a rapidapp-made widget !
Both processes communicate in the shared memory arena.
You can develop your vk things with rapidapp, separately develop your
Performer program, set a structure in a Shared arena for encapsulating orders
from vk buttons, and everything goes OK.
It seems so simple, so why wasn't this proposed as a solution for combining
Motif with Performer ? Is that a bad method ?
Mike
===================================List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:01 PDT