Hello,
Looks good to me.
There are a couple of things missing in FindWt.cmake but I spent the
weekend backporting for Debian Lenny and playing with the OpenSuse
Build Service and didn't have time to work on FindWt.cmake:
* Search for the debug libraries in /usr/lib/debug/usr/lib. This is
done by chaging these lines:
FIND_LIBRARY( Wt_DBO_DEBUG_LIBRARY NAMES wtdbod PATHS PATH
PATH_SUFFIXES lib lib-debug lib_debug )
to
FIND_LIBRARY( Wt_DBO_DEBUG_LIBRARY NAMES wtdbod PATHS PATH
PATH_SUFFIXES lib lib-debug lib_debug HINTS /usr/lib/debug/usr/lib )
But IIRC, HINTS was introduced in CMake 2.6. Also, "PATHS PATH" is not
needed since CMake 2.6 (maybe even since 2.4.something), I can't
remember now.
* Support the normal name (without 'd' suffix) for the debug libraries:
FIND_LIBRARY( Wt_DBO_DEBUG_LIBRARY NAMES wtdbod wtdbo PATHS PATH
PATH_SUFFIXES lib lib-debug lib_debug HINTS /usr/lib/debug/usr/lib )
* Support debug and release libraries in the same project, very useful
for Visual C++ and maybe Eclipse. This requires some more complex
coding:
IF( Wt_DBO_LIBRARY_DEBUG AND Wt_DBO_LIBRARY_RELEASE )
# if the generator supports configuration types then set
# optimized and debug libraries, or if the CMAKE_BUILD_TYPE has a value
IF( CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE )
SET( Wt_DBO_LIBRARIES optimized
${Wt_DBO_LIBRARY_RELEASE} debug ${Wt_DBO_LIBRARY_DEBUG} )
ELSE( CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE )
# if there are no configuration types and CMAKE_BUILD_TYPE has no value
# then just use the release libraries
SET( Wt_DBO_LIBRARIES ${Wt_DBO_LIBRARY_RELEASE} )
ENDIF( CMAKE_CONFIGURATION_TYPES OR CMAKE_BUILD_TYPE )
ELSEIF( Wt_DBO_LIBRARY_RELEASE )
SET( Wt_DBO_LIBRARIES ${Wt_DBO_LIBRARY_RELEASE} )
ELSE( Wt_DBO_LIBRARY_DEBUG AND Wt_DBO_LIBRARY_RELEASE )
SET( Wt_DBO_LIBRARIES ${Wt_DBO_LIBRARY_DEBUG} )
ENDIF( Wt_DBO_LIBRARY_DEBUG AND Wt_DBO_LIBRARY_RELEASE )
That needs to be done for each library
On Wed, Apr 14, 2010 at 4:09 AM, Mike Teehan <[email protected]> wrote:
> FindWt.cmake doesn't check for any of the dbo stuff. The attached patch
> works,
> at least for me.
>
> Mike
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
>
--
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
