Thanks Dave and others,
I fgiured out how to create the binary package. It is quite simple. As you mentioned about the .so files, one just needs to copy the required .so files into the directory and export the PATH as done in the script. Best, Dhruv --- Dave Neary <[EMAIL PROTECTED]> wrote: > > Hi Chopra, > > chopra dhruv wrote: > > I agree it can be harmful. But I am confused, how > > else do I generate the wengophone binary package > like > > the one given at http://www.openwengo.com/ > > I thought static linking with the boost library > was > > the answer.. > > The binary package includes the script file > "wengophone.sh" which > resolves the symlinks which are made to the real > binary, and then runs > it with the command line: > export > LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:${WENGOPHONEDIR}" > > cd ${WENGOPHONEDIR} > exec ./qtwengophone -style=plastique > > During the binary package creation, the script > copy_gnulinux_libs.py > also gets run, and this copies all required .so > files into the same > directory as the qtwengophone binary. These then get > found when > LD_LIBRARY_PATH is set as above. > > I'm not sure what exactly generated the binary > package, it's part of the > buildbot set-up, but Mathieu Stute could certainly > tell you. > > Cheers, > Dave. > > -- > Dave Neary > OpenWengo Community Development Manager > Email: [EMAIL PROTECTED] > Tel: +33 9 51 13 46 45 > Mob: +33 6 28 09 73 11 > ____________________________________________________________________________________Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ _______________________________________________ Wengophone-devel mailing list [email protected] http://dev.openwengo.com/mailman/listinfo/wengophone-devel
