search for: 3rdpartylibname

...et why CMake insists on checking every known function prototype of for example "recv" and for the presence of headers it (or the project dev!) should know are not there. As for 3rdparty libraries: provide an option like autotools (about the only thing (sometimes) done right) "--with-3rdpartylibname=somePath". Leave it to the user/builder to get their setup right and provide the correct library (location) Sorry for the somewhat off-topic ramble :s. Ruben

...ort. 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 autotools (about the > only thing (sometimes) done right) "--with-3rdpartylibname=somePath". > Leave it to the user/builder to get their setup right and provide the > correct library (location) This is not so easy. The user can replace anything you can imagine of. From the compiler itself to core OS functionality. IIRC there are cases of people using a third-party C...

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, there is quite a bit of variation on Windows too. Apart from the

Op 5 jan. 2011 19:33 schreef "Anton Korobeynikov" <anton at korobeynikov.info> het volgende: > > > contains most of them. If they're non-trivial (like the ones I needed to > > add for OSX functionality) that's a different story. > FWIW the difference is even more significant on, e.g. mingw32 because > process spawning is pretty much expensive and

...wo 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 autotools (about the >> only thing (sometimes) done right) "--with-3rdpartylibname=somePath". >> Leave it to the user/builder to get their setup right and provide the >> correct library (location) > > This is not so easy. The user can replace anything you can imagine > of. From the compiler itself to core OS functionality. IIRC there are > cases of pe...