On 28/10/2015 22:03, SeVlaT wrote: > > > For information here are the project type ID that I know about so > far: > > > > Solution Folder: 2150E333-8FDC-42A3-9474-1A3956D46DE8 > > Visual C/C++ Project: 8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942 > > Visual Basic Project: F184B08F-C81C-45F6-A57F-5ABD9991F28F > > Python Project: 888888A0-9F3D-457C-B088-3A5042F75D52 > > Fortran Project: 6989167D-11E4-40FE-8C1A-2192A86A7E90 > > It looks like Yvan Rodrigues has done some of the work on project type > GUID's here: > > > http://www.codeproject.com/Reference/720512/List-of-Visual-Studio-Project-Type-GUIDs > > <http://www.codeproject.com/Reference/720512/List-of-Visual-Studio-Project-Type-GUIDs> > > > Yes, {8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}, that used in vc10-vc12 > directories, is a "Visual C/C++ Project" guid, > but vc14 {59348fde-2f50-426c-9f74-184aa069c067} is unknown guid. Is it > an error?
Yes. > > Now I am researching mpir_config.py scripts and developing property > sheet structure. > I made a copy of build.vc12 directory - build.vc12.p, but with my > solution, projects, and property sheets, and do my work in this new > directory (and also in build.vc) > You may see it in my repository, branch msvc_props: > https://github.com/sevlat/mpir/tree/msvc_props > > When I'll finished a property sheet structure, I'll begin to adapt > mpir_config.py. I suppose it'll became shorter and simplie, because an > considerable part of mpir_config-s logic is now performed by property > sheets. > > The next question about mpir_config.py. > What is "app_type"? Does it really used, or will be used in future? > If does, the following code probably contain an error (line 470). > > if proj_type == app_type: > s1 = 'DEBUG;WIN32;_CONSOLE' > s2 = '' > if proj_type == dll_type: > s1 = 'DEBUG;WIN32;HAVE_CONFIG_H;MSC_BUILD_DLL;' > s2 = 'DLL' > elif proj_type == lib_type: > s1 = 'DEBUG;WIN32;_LIB;HAVE_CONFIG_H;' > s2 = '' > else: > pass > if plat == 'x64': > s1 = s1 + '_WIN64;' > > s1 for dll and lib ends with semicolon, but s1 for app doesn't. We'll > possibly get a wrong result in the last line of this flagment. Yes, all the s1 strings should end with a semicolon. The three different builds are *.exe (app_type), *.dll (dll_type) and *.lib (lib_type). 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 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.
