Thank you for a detailed answer. In general, I totally agree with you.
it would hence > be desirable to modify mpir_config.py to generate your simpler *.vcxproj > files and also generate any property sheets that contain details that > depend on processor architectures. This is certainly possible but it is > not a trivial exercise > > You might however want to tackle this yourself as it would make it easy > to maintain your alternative build approach and also provide an easy way > of switching between and comparing the two approaches. > I'll try to do that. I looked into mpir_config.py and I suppose it is not very difficult or time-taking to modify mpir_config.py. Could you explain, why all four mpir_config.py looks for source files in directory 'build.vc12' (see line 45) Is it an error? May be there should be a version corresponding directory: 'build.vc10', 'build.vc11' etc. ? It seems to me, this item may be totally deleted from the list. Because build.vcNN directories contains no source files - all existing *.c and *.h files are listed in exclude_file_list (see line 50), so mpir_config.py takes nothing from build.vcNN directory. Best regards, Sergey Taymanov -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
