On 03/11/2015 10:21, SeVlaT wrote: > Can anybody explain mpir_config.py command line parameters? > > It expect at most one parameter - a number. If it doesn't have a second bit, > the program will exit after doint allpreliminary job, but before asking user > about desireble processor architecture. If it have both bits 1 and 2 the > program works the same way then without any command line parameter.
All Python programs have at least one parameter because the program's name is put in argv[0] automaticaally when it is launched. So a program that has no command line parameters will have len(argv) == 1. Normally mpir_config.py is called with no command line parameters and it then asks the user for their desired architectures. When it is called with a parameter it does the preliminary work to create files such as config.h, longlong.h, ... but it does not build the MSVC project files. This is because mpir_config.py was used in two build systems - the Visual Studio build system and the MSDOS based command line build - and the latter build needs the preliminary work but not the MSVC project part of mpir_config.py. But the MSDOS based build is not being maintained at the moment so for use with MSVC, which I believe is your interest, mpir_config.py is called with no command line parameters. Brian -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
