Carbider | 16 October, 2007 15:01

After unsatisfactory attempt to port BlueZ system to Symbian due to <sys/signal.h> differences, David advised me to look at P.I.P.S libraries. P.I.P.S. are Symbian libraries that are compatible with POSIX standard.

http://developer.symbian.com/wiki/display/oe/P.I.P.S.+Home

That could mean reducing efforts while migrating the project to mobile device.

That was true on several positions. But there still was a trouble with <sys/system.h>.

It has sigaction{} structure inside. But BlueZ needs sigaction() function too.

I don’t know, if the trouble is that BlueZ doesn’t support POSIX. Or it is a Symbian’s trait.

But there is a paragraph here http://developer.symbian.com/wiki/download/attachments/1411/PIPS_Essential_Booklet.pdf

[PIPS_Essential_Booklet.pdf]

Which says: “The P.I.P.S. environment does not support signals”.

Other functions that are not supported:

sigfillset()

sigdelset()

I had to examine what Signals are used for. I came to conclusion that they are used to halt child processes.

Sigaction()function was used to specify the action to be associated with a specific signal. After that the process generates his child instance (with fork and exec) which can be killed by sending “halt” signal with this statement:

kill(pid, SIGHUP)

So, I did not still find the replacement to this function to kill child processes. I’m thinking about Symbian’s RProcess class. Any ideas?

I found that Carbide C++ is very strict to data types. Even more strict than unix c.

I had to replace statements like:

struct bnep_setup_conn_req *req;

req = (void *) pkt;

req = (struct bnep_setup_conn_req *) pkt;

At this 2 documents:

http://www3.symbian.com/faq.nsf/0/D23BCB0AF8B1DC168025729F003FF465?OpenDocument

http://www3.symbian.com/faq.nsf/0/0C3AC88AA406F6108025729F00402E3A?OpenDocument

I found recommendations how to substitute ther “fork”, “exec” operations with other posix functions. The main is posix_spawn().

I tried to follow this idea, outflanking the forks and execs with posix_spawn().It worked well.

At run_script() function there is instruction:

execv(script, argv);

Before run_script()is used, the fork()function is called to create the instance of program itself.

This “execv+fork”pair is replaced by one

posix_spawn(&Childpid,script,NULL,NULL,argv,NULL);

call.

There are still lots of goals to reach. I don’t know how to pass command line arguments to Carbide’s console application.

The sdp.c is not implemented in this version of port because it still makes too much errors and it will take time to solve.

I think there will be resulting GUI application which will run main PAND console instances. After that they should get into single signed SIS installation file.

Please look the sources of port using P.I.P.S. at my CVS repository http://bluspan.cvs.sourceforge.net/bluspan/pand_port_06/

The CVS checkout process to Carbide C++ IDE is described in my post: Get project from CVS to Carbide C++.

Please, checkout the newest pand_port_06 version.