It LOOKS right, so the remaining thought I have is to try tracing the program on the device to see how it's doing the loading.
Don't ask me how to do that though >.> I don't know. /s/ Adam On Thu, Apr 12, 2012 at 7:17 AM, Felipe Crochik <[email protected]> wrote: > Hi, > First of all: thank you! > I tried removing webkit from QT += and adding: > > INCLUDEPATH += /usr/include/qt4/QtWebKit > > LIBS += -L/opt/GApp/lib -Wl,-rpath,/opt/GApp/lib -lqtwebkit > > > It built OK but on the device still uses the "standard" webkit library on > /usr/lib > > Did I get anything wrong? > Felipe > > > > On Wed, Apr 11, 2012 at 10:30 PM, Coda Highland <[email protected]> wrote: >> >> LD_LIBRARY_PATH is probably taking a back seat to the rpath set in your >> binary. >> >> I would recommend taking QT+=webkit out of your .pro file and manually >> adding the include paths and linker flags, so that you can specify the >> rpath linker flag explicitly to a different path. >> >> /s/ Adam >> >> On Wed, Apr 11, 2012 at 8:39 PM, Felipe Crochik <[email protected]> >> wrote: >> > Since there is a regression with PR1.2 (autosizecontents) I am trying to >> > find a work around so I can distribute my application. My goal is to use >> > the >> > "qt on the device" + "libwebkit.so" (from PR1.1) without changing any of >> > the >> > shared libraries on the device. >> > >> > I just tested using the libqtwevkit.so from the package on the SDK >> > (libqtwebkit4_2.1.1~git20110418-0maemo2+0m6_armel.deb) and it works just >> > fine. Now the challenge is how to deploy it without affecting any other >> > applications. >> > >> > I am copying the libQtWebKit.so.4 to a sub folder of my application >> > (/opt/GApp/lib) and I tried without success: >> > >> > 1. "export LD_LIBRARY_PATH=/opt/GApp/lib" and then running my >> > application >> > using the x-terminal >> > 2. changing the source code of my application to include >> > "QCoreApplication::addLibraryPath("/opt/GApp/lib");" >> > 3. changing the PATH to start with "my lib" folder and then running my >> > application. >> > >> > On all 3 cases the application used the "official" webkit and not "my >> > version". >> > >> > So far the only way I managed to have my application use the >> > "alternative" >> > webkit was by changing the symbolic link on /usr/lib/libQtWebKit.so.4 to >> > point to "my" webkit version. >> > >> > What is the correct/recommended way? Since I am using the "official" 1.1 >> > package I assume it expects to be installed to /usr/lib ...don't know if >> > this is the problem or not. >> > >> > BTW, I am not using the qml webview. >> > >> > Thanks in advance, >> > Felipe >> > >> > _______________________________________________ >> > webkit-qt mailing list >> > [email protected] >> > http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt >> > > > _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
