search for: hard_coded_results_vc

...does not mean that it is present on another future or past version. The same could be said for the Unix case. Hard-coding that information defeats the purpose of platform checks. We could hard-code some check results with if( NOT WIN32 ) checks elseif( MINGW ) hard_coded_results_mingw else hard_coded_results_vc endif() but that adds noise and increases fragility and maintenance effort. For just saving two or three minutes while configuring, something that most people don't do often (except if you are one of the build maintainers, of course ;-) > As for 3rdparty libraries: provide an option like a...

2011/1/5 Óscar Fuentes <ofv at wanadoo.es>: > Ruben Van Boxem <vanboxem.ruben at gmail.com> writes: > >> And this is why I don't understand configure checks for windows... There's >> only one/two header/library sets... The Windows SDK and MinGW. This info >> should be built in IMHO... > > Although the panorama is not so diverse as the Unix world,

...rong point in the Windows API, backwards compatibility is almost infinite! Unix, well, that seems to be a completely different story :s... > > We could hard-code some check results with > > if( NOT WIN32 ) >  checks > elseif( MINGW ) >  hard_coded_results_mingw > else >  hard_coded_results_vc > endif() > > but that adds noise and increases fragility and maintenance effort. For > just saving two or three minutes while configuring, something that most > people don't do often (except if you are one of the build maintainers, > of course ;-) > >> As for 3rdpart...