On 4/1/07, E. Wing <[EMAIL PROTECTED]> wrote:
> Maybe this could be implemented in a major release of CMake, thus > developers would be aware that changes are required to their scripts. > As soon as it is advertized enought, it's ok. I'm more inclined to leave the current behavior, and when SDL 1.3 finally rolls around, try a fresh start then since we'll most likely need a new script for that anyway.
Yes, that's ok with me.
Currenly, under Windows, when I click on the configure button in CMAKE, it > says:
- It says, "I did not found SDLMAIN_INCLUDE, SDLMAIN_LIBRARY, > SDLIMAGE_INCLUDE, SDLIMAGE_LIBRARY" > - I set those variables, > - click on configure one more time. > So I need more details about how CMake does this. I don't understand how CMake determines which ones to nag you about. The nags I get are different than yours.
I can't give you the explanation about it. Do you know someone who could explain it to us?
And what about calling that variable SDL_LIBRARY_DIR (with for example the value "c:\My project\lib") and deducing from that all the other variables.
No, deduction can fail. There may be a case where SDLmain and SDL are located in different directories. There is also the case that the libraries are not named what we expect. Thus, each one requires their own field to handle these cases, as they do now. And this is the reason for the complexity.
Well, I leave it to you, as long as, once all the "required" variables are set, things compile. Regards, -- Pierre-André Galmes Free Software consultant StarXpert - www.starxpert.fr 6, rue Eugène Varlin - 75010 Paris
_______________________________________________ CMake mailing list CMake@cmake.org http://www.cmake.org/mailman/listinfo/cmake
