MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005807CMakeModulespublic2007-09-30 15:442011-05-02 14:46
Reporterluca 
Assigned ToEric Wing 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in VersionCMake-2-6 
Summary0005807: FindSDL_image.cmake defines to "YES" the variable SDLIMAGE_LIBRARY instead of SDL_image_FOUND
DescriptionWhen trying to locate the SDL_image library with

FIND_PACKAGE(SDL_image)

the used script FindSDL_image.cmake defines to "YES" the variable SDLIMAGE_LIBRARY instead of SDL_image_FOUND, as it should be as stated in the CMake documentation in the FIND_PACKAGE section:

"<name>_FOUND will be set to indicate whether the package was found"

Steps To Reproduce
Additional InformationNew code was checked in a few weeks ago which rewrites the FOUND section anyway so I think it's already fixed.

TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2007-09-30 15:44lucaNew Issue
2007-12-17 21:33Bill HoffmanStatusnew => assigned
2007-12-17 21:33Bill HoffmanAssigned To => Eric Wing
2008-01-03 04:41Eric WingNote Added: 0010054
2008-01-03 04:44Eric WingResolutionopen => fixed
2008-01-03 04:44Eric WingAdditional Information Updated
2011-01-18 12:05David ColeNote Added: 0024878
2011-01-18 12:05David ColeStatusassigned => resolved
2011-01-18 12:05David ColeFixed in Version => CMake-2-6
2011-05-02 14:46David ColeNote Added: 0026362
2011-05-02 14:46David ColeStatusresolved => closed

Notes
(0010054)
Eric Wing   
2008-01-03 04:41   
Really? I can't verify this. I don't see this in my oldest copy of the code (and all the SDL modules are pretty similar so I'm surprised they don't all have the same problem).

But I checked in a bunch of fixes a few weeks ago and this section has been rewritten anyway so I think it's fixed now one way or another.
(0024878)
David Cole   
2011-01-18 12:05   
Resolving as fixed since the comment says "I think it's fixed now one way or another." (And there's been no further information added since January, 2008... Over 3 years ago now..)
(0026362)
David Cole   
2011-05-02 14:46   
Closing resolved issues that have not been updated in more than 3 months.