From: Harald O. <har...@el...> - 2012-12-07 08:22:48
|
Am 07.12.2012 08:47, schrieb Trevor Davel (Twylite):> Hi, > > On 2012/12/06 07:29 PM, Donald G Porter wrote: >> Empirically you and Jos Decoster are the only folks who complain about >> ability to build using MSVC (maybe Twylite too?). I imagine your >> voices represent multitudes, but still those are the only folks I have >> evidence for caring about nmake builds. > Yep, me too ;) But to be honest I'd rather be building with CMake, and > I don't care much about the ability to build extensions against an > installed runtime (rather than against sources and binaries in a build > environment), because that's mostly broken with MSVC anyway. How does the CMAKE build work ? Should we pass from nmake to cmake ? > >> If the nmake crowd can live with fragile warnings not to build/test >> in paths with spaces, I'm not going to more effort to overrule that. > I can live with this. I don't test in the build/test environment > anyway, because it gives a false sense of security. Tests need to be > executed using the final installed configuration, and preferably on a > system without MSVC installed. This way you get to confirm that you > included the correct C runtime in your install, that DLLs and packages > can be located correctly, and that core functionality can be reasonable > expected to work in a production environment. Yes, but this is another purpose. The test suite will tell you, if you have done something wrong in your code. Both tests are helpful. At least, I tried to get the test suite work in the installation folder, which tells you, if the build is correct (and stresses your nerves to make this work). Harald |