By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release. View | Details | Raw Unified | Return to bug 1622
Collapse All | Expand All

(-)a/ConfigureChecks.cmake (-3 / +10 lines)
Lines 172-186 if( WITH_XSCREENSAVER ) Link Here
172
      pkg_search_module( XSS xext )
172
      pkg_search_module( XSS xext )
173
    endif( )
173
    endif( )
174
  endif( )
174
  endif( )
175
175
  check_include_file( X11/extensions/scrnsaver.h HAVE_XSCREENSAVER_H )
176
  check_include_file( X11/extensions/scrnsaver.h HAVE_XSCREENSAVER_H )
176
  if( HAVE_XSSLIB AND HAVE_XSCREENSAVER_H )
177
  if( HAVE_XSSLIB AND HAVE_XSCREENSAVER_H )
177
    set( HAVE_XSCREENSAVER 1 )
178
    set( HAVE_XSCREENSAVER 1 )
178
  else( )
179
  else( )
179
    tde_message_fatal( "xscreensaver is requested, but was not found on your system" )
180
    tde_message_fatal( "xscreensaver is requested, but was not found on your system" )
180
  endif( )
181
  endif( )
182
183
  # We don't really need the xscreensaver package for build, we only must know 
184
  # there xscreensaver stores its executables. So leave user the posibility 
185
  # to define XSCREENSAVER_DIR to so let the user.
181
  include( FindXscreensaver.cmake ) # not really good practise
186
  include( FindXscreensaver.cmake ) # not really good practise
182
  if( NOT XSCREENSAVER_FOUND )
187
  if( NOT XSCREENSAVER_DIR )
183
    message( FATAL_ERROR "\nxscreensaver is requested, but was not found on your system" )
188
    tde_message_fatal( 
189
      "xscreensaver is requested, but cmake can not determine the location of XSCREENSAVER_DIR
190
 You have to either specify it manually with e.g. -DXSCREENSAVER_DIR=/usr/lib/misc/xscreensaver/
191
 or make sure that xscreensaver installed properly" )
184
  endif( )
192
  endif( )
185
endif( )
193
endif( )
186
194
187
- 

Return to bug 1622