| Summary: | SDL2.m4 shares same variables as SDL.m4 so they cache values | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Edgar Simo <bobbens> |
| Component: | *don't know* | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED FIXED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | HG 2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Attachments: | Replaces SDL_CONFIG with SDL2_CONFIG in sdl2.m4 to allow AM_PATH_SDL2 to work with AM_PATH_SDL independently | ||
Fixed, thanks! http://hg.libsdl.org/SDL/rev/98de3e4f1c36 |
Created attachment 1240 [details] Replaces SDL_CONFIG with SDL2_CONFIG in sdl2.m4 to allow AM_PATH_SDL2 to work with AM_PATH_SDL independently So basically the issue is that: AC_PATH_PROG(SDL_CONFIG, sdl2-config, no, [$PATH]) in sdl2.m4 shares the same variable (SDL_CONFIG) as sdl.m4: AC_PATH_PROG(SDL_CONFIG, sdl-config, no, [$PATH]) What happens is if you run the AM_PATH_SDL2 and then AM_PATH_SDL to say fall back on SDL if SDL2 isn't found, the AM_PATH_PROG command gets cached (ac_cv_path_SDL_CONFIG) so that unless you unset this cache variable, the result for AM_PATH_SDL will be EXACTLY the same as for AM_PATH_SDL2. To fix I would recommend renaming SDL_CONFIG to SDL2_CONFIG in sdl2.m4, replacing all instances so it won't cache to the same variable. Attaching a tested patch that fixes this.