Re: [Barry-devel] New tool: btarcmp (and other news)

[Toby G. <tob...@re...>]

On 24/01/12 20:49, Nicolas wrote:
> Le mardi 24 janvier 2012 à 13:23 +0000, Toby Gray a écrit :
> No link with Barry.
>
> I'm interested in QNX port.
>
> Which QNX framework do you use ? pkgsrc ?

I don't use pkgsrc as it didn't appear to provide pre-build packages for 
any architecture other than i386. I've been manually building the 
dependent libraries.

I'm currently building on QNX 6.5.0, which I think is the pre-Playbook 
release of QNX. I'm just using the standard QNX SDK and compiling using:

export CONFIG_TARGET="i486-pc-nto-qnx6.5.0 # or 
"arm-unknown-nto-qnx6.5.0" or "sh-unknown-nto-qnx6.5.0"
./buildgen.sh
PKG_CONFIG=false qconfig -r "./configure --host=$CONFIG_TARGET 
--prefix=$BARRY_ROOT --with-libusb1_0=$LIBUSB_ROOT 
--with-libiconv-prefix=$LIBICONV_ROOT"
qconfig -r "make"
qconfig -r "make install"

> I think to start a new project for my PlayBook device : a DLNA player.
> And I study how to port glib2, gupnp-* into the QNX system.

I'd imagine it shouldn't be too difficult to do, although it depends how 
well the configure script for gupnp-* has been written to handle 
cross-compilation. Barry's configure script was already written in a way 
which supported cross compilation easily and so I only needed to add a 
few tweaks (such as POSIX network APIs needing an extra linker library).

On the other hand I've come across several projects which have been far 
more tricky to cross compile. They aren't major problems to fix, such as 
changing 'gcc' to '$CC' in make files or avoiding using AC_CHECK_FILE in 
the configure script (as it always fails if cross compiling).

Native QNX projects (at least pre-Playbook QNX) tend to shy away from 
using configure (see 
http://www.qnx.com/developers/docs/6.4.0/neutrino/prog/make_convent.html) but 
you can get the QNX build system to call configure for you (see 
http://www.qnx.com/developers/docs/6.4.0/neutrino/prog/make_convent.html#GNU_configure).

I wouldn't be surprised if this all changes for building Playbook 2.0 
NDK applications though, I've not been following the news to do with this.

I hope some of this information helps, it's a bit of a brain dump so let 
me know if you want further information.

Regards,

Toby