On 23-3-2014 15:17, Markus Engel wrote:
Why don't you use a vm?
Ease of use / laziness. It would help if I could share diskspace from host to VM, so only the compilation is done on the VM, but I still have the file handling / bzr / etc. from Windows. Haven't looked into how to do that. We will change compiler anyway on Windows after the release, to switch to C++11. We could then choose a compiler with clang compatible EH for the devlibs. I look forward to playing with clang's static and dynamic analyzers. Anybody using those yet? clang's refactoring tools,... *sigh*
Later we should make sure that we let configure automatically choose warning options depending on the used compiler: warning: unknown warning option '-Wno-unused-but-set-variable'; did you mean '-Wno-unused-variable'? [-Wunknown-warning-option]
../../trunk/src/gradient-drag.cpp:1491:26: warning: comparison of constant -1 with expression of type 'GrPointType' is always false [-Wtautological-constant-out-of-range-compare] (point_type == -1 || da->point_type == point_type) &&
Definitely a bug waiting to happen (if not already).
../../trunk/src/extension/internal/emf-print.cpp:948:49: warning: variable 'i' is uninitialized when used here [-Wuninitialized] for(int i; cit != pathRect.end_open();++cit,i++) { ^ ../../trunk/src/extension/internal/emf-print.cpp:948:14: note: initialize the variable 'i' to silence this warning for(int i; cit != pathRect.end_open();++cit,i++) { ^ = 0
:'(
I could provide you with a list of warnings emitted by clang, if you want me to :) .
Please send it to the list. To further drill on people's heads to look at warnings and enable -Werror. Can I move you to provide some fixes for those too? :-)
Thanks a lot, Johan