>
> Unless your hobby is setting up build files or configure
> scripts, I am afraid the latest CVS commit will draw your
> attention to an unpleasant change.
>
> Until now, Wt installed its include files directly into the
> (...)/include folder, where "(...)" corresponds to
> ${CMAKE_INSTALL_PREFIX} as configured when building/installing Wt.
> Because this clobbers the include directory, the new CVS
> version of Wt installs its headers in (...)/include/Wt.
>
Actually, I applaud the change. I was wondering if it was just me or not.
Making this change does get Wt to conform to the 'natural' way of doing
things.
#include <Wt/WLineEdit>
Is how most of my other libraries work, where /usr/local/include is
typically defaulted in the development environment, and as such, no special
include directories need then be defined.
--
Scanned for viruses and dangerous content at
http://www.oneunified.net and is believed to be clean.
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
