Hello Sergey,

Feel free to add this information to our wiki pages - everyone has
write access on them.
http://www.webtoolkit.eu/wt/wiki/

I'm not sure if I would place this under 'Installation instructions'
or 'Tutorials', but put it somewhere and we can move it around later.

Note that Wt does have a way to set the installation prefix, it is
called CMAKE_INSTALL_PREFIX, which is standard for all cmake programs.

Regards,
Wim.

2008/10/24 sergey bryukov <[EMAIL PROTECTED]>:
> Build and deploy Wt based application or cross Wt compiling
>
> wt2.2.0 + boost1_35
>
> This post propose an approach how-to deploy Wt based application with all
> dependences build on your development host as set of executable and library
> files in one folder.
>
> Create folder tree as below, src could be place of your supplication courses
> :
>
> /prj/
>
>    bin/
>
>    src/
>
>    tools/
>
>       include/
>
>       lib/
>
> Let take in to consideration your project depend on wt2.2.0 and wt should
> depend on boost1_35. So, It could be convenient to do not install libraries
> to the /usr/ but keep them near your src and deploy them together as bundle.
>
> 1. build boost-1_35:
>
> cd boost_1_35
>
> ./configure --prefix=/home/surge/prj/tools/ --without-
> libraries=python,wave,test
>
> make install
>
> boost should be placed into prj/tools/ and fill up include/ and lib/ folder
>
> 2. build wt-2.2.0:
>
> cd wt-2.2.0
>
> mkdir build; cd build
>
> cmake -D BOOST_DIR=/home/surge/prj/tools/ -D BOOST_COMPILER=gcc41 -D
> BOOST_VERSION=1_35 -D LIB_INSTALL_DIR=/home/surge/prj/tools/lib ../
>
>           make
>
>          sudo make install
>
> as wt-2.2.0 configure script doesn't provide include's install place switch,
> wt include files will installed to /usr/local/include/wt, this is why sudo
> is needed. Next is:
>
> cp -rf /usr/local/include/Wt /home/surge/prj/tools/include/
>
>
> 3. build an application
>
> As project tree contain all needed dependences:
>
> /prj/
>
>    bin/
>
>    src/
>
>    tools/
>
>       include/
>
>         boost-1_35/
>
>         Wt/
>
>     lib/
>
>        libboost*.a
>
>        libwt*.so
>
> Configure your build environment to utilize include and libs from tools/
> folder. It could be looks like below :
>
> -I../tools/include/boost-1_35
>
> -I../tools/include
>
> -L../tools/lib
>
> 3. Deploy
>
> For success deploy you need to distribute all libwt*.so from tools/lib/
>
> and add path to libraries:
>
> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/path/to/libwt/
>
> Deploy some recourse from your building host to the server's same place
>
> /usr/local/share/cmake-2.4/Modules/FindWt.cmake
>
> /usr/local/share/Wt//resources
>
> /etc/wt/wt_config.xml
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to