I know that Webuser and Webgroup sets what user and group the WtHttp server 
uses, and rundir, is the directory the Wthttp server is applied and run un. 
connector_http has to be a linking to the server as well. Connector_fcgi is a 
linking to fast cgi (graphics protocol/application for web server). 
Userlib_prefix has to be the prefix to where you find the Wt library files, and 
adding that to Cmake_install_prefix would result in the Wt library being 
installed in /usr/local/lib. Configdir is where the Wt config file goes. Shared 
libs and Multi threaded I have a feeling what they do, but not enough that Im 
able to explain it well.
Its really not too difficult to understand these options, but it helps to have 
done 10-20 Wt installs in a month or two :) I really didn’t have a clue when I 
started out in the end of january this year, now I know a bit more, but I still 
struggle sometimes :)

Regards
Tor

2. apr. 2014 kl. 18:30 skrev Thomas Suckow <thomas.suc...@pnnl.gov>:

> I would be interested to know what the following does, it should locate 
> boost itself:
> 
> cmake \
> -D MULTI_THREADED=ON \
> -D RUNDIR=/var/www/wt \
> -D WEBUSER=www-data \
> -D WEBGROUP=www-data \
> -D SHARED_LIBS=ON \
> -D CONNECTOR_FCGI=OFF \
> -D CONNECTOR_HTTP=ON \
> -D USERLIB_PREFIX=lib \
> -D CONFIGDIR=/etc/wt \
> -D CMAKE_INSTALL_PREFIX=/usr/local \
> ../
> 
> On Wed 02 Apr 2014 06:33:03 AM PDT, Tor Arne Fallingen wrote:
>> Hey all.
>> 
>> It seems every time I try and download and install Boost and Wt either on 
>> Debian Wheezy (Rpi) or Ubuntu (Virtualbox) I end up encountering a problem 
>> when I get to the cmake part of the Wt install. I follow the guide found at 
>> http://blog.raymond.burkholder.net/index.php?/archives/539-Installing-Wt-v3.3.0-on-Debian-Wheezy.html
>>  and I modify the cmake from:
>> 
>> cmake \
>> -D MULTI_THREADED=ON \
>> -D RUNDIR=/var/www/wt \
>> -D WEBUSER=www-data \
>> -D WEBGROUP=www-data \
>> -D BOOST_ROOT=/usr/local \
>> -D BOOST_LIBRARYDIR=/usr/local/lib \
>> -D BOOST_INCLUDEDIR=/usr/local/include/boost \
>> -D SHARED_LIBS=ON \
>> -D CONNECTOR_FCGI=OFF \
>> -D CONNECTOR_HTTP=ON \
>> -D USERLIB_PREFIX=lib \
>> -D Boost_USE_STATIC_LIBS=OFF \
>> -D Boost_USE_STATIC_RUNTIME=OFF \
>> -D CONFIGDIR=/etc/wt \
>> -D CMAKE_INSTALL_PREFIX=/usr/local \
>> ../
>> To where boost actually is (on my current virtual box rip):
>> 
>> cmake \
>> -D MULTI_THREADED=ON \
>> -D RUNDIR=/var/www/wt \
>> -D WEBUSER=www-data \
>> -D WEBGROUP=www-data \
>> -D BOOST_ROOT=/usr \
>> -D BOOST_LIBRARYDIR=/usr/lib \
>> -D BOOST_INCLUDEDIR=/usr/include/boost \
>> -D SHARED_LIBS=ON \
>> -D CONNECTOR_FCGI=OFF \
>> -D CONNECTOR_HTTP=ON \
>> -D USERLIB_PREFIX=lib \
>> -D Boost_USE_STATIC_LIBS=OFF \
>> -D Boost_USE_STATIC_RUNTIME=OFF \
>> -D CONFIGDIR=/etc/wt \
>> -D CMAKE_INSTALL_PREFIX=/usr/local \
>> ../
>> But without fail I get the annoying message:
>> 
>> CMake Error at CMakeLists.txt:371 (MESSAGE):
>>  Could not find a boost installation in /usr/lib.
>> 
>> But all the *.so library files are in that folder, and even going through 
>> CMakeCache.txt and manually entering all paths doesn’t help me. I have 
>> managed to fix it every time so far, but its been kind of so much back and 
>> forth into files and directories that I really haven’t been able to make an 
>> efficient note of what actually fixed it, and now Im there again, wishing I 
>> had some notes from last time :)
>> So, does anyone have any solution that works?
>> 
>> Regards
>> Tor
>> 
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest

Reply via email to