Hi Dennis. The wklauncher (aka "owb") is integrated into the cmake based
webkit library build, builds alongside it with dependencies into the
build results directory structure, and ends up in the same build results
directory. One of its main purposes is to test the webkit library that
it gets built with. So as-is it does need to be built with all of
webkit.

If you want an example of a browser app that links against webkit but is
not part of the webkit build, see the webkit_kd launcher used for QNX
CAR. A copy of it can be found in the web-browsers source repository
under qnx/trunk/. It has a regular QNX recursive Makefile build
structure, but with dependencies to webkit libs and headers that you
must satisfy manually, for example by using symbolic links from a
staging directory to a webkit build.

So you're right that the entire webkit does not need to be built, but it
makes pulling in headers much easier if it has at least been configured
(which creates subdirectories of links to required headers).

Max

-----Original Message-----
From: Dennis Kellly [mailto:community-noreply@qnx.com] 
Sent: Monday, March 29, 2010 10:45 AM
To: general-web_browsers
Subject: Customizing wklauncher

I need to build a custom version of wklauncher.  Since it links to
supplied binary shared libraries, there seems no logical reason why the
entire webkit should need to be built, but docs say it does .   (Kind of
like saying you need to build the o/s to compile 'hello world'...what am
I missing?)

There are two perl packages (one from crank) but the docs don't really
say what the relationship between them is - just that you need them.  I
have been unable satisfy perl 'include' requirements to get configure to
run without error.  Any hints?

Thanks,
Dennis



_______________________________________________

General
http://community.qnx.com/sf/go/post50697