Menu
▾
▴
xml-cppdom-devel
|
From: Doug M. <mc...@ia...> - 2009-07-02 16:54:18
|
Hello, What is the appropriate architecture type to specify for scons to build cppdom 1.0.0 for win x64? Thanks. Doug |
|
From: Patrick H. <pa...@13...> - 2009-07-02 18:02:06
|
x64 should do it, but it's been a long time since I last tried it. -Patrick On Jul 2, 2009, at 11:03 AM, Doug McCorkle wrote: > Hello, > > What is the appropriate architecture type to specify for scons to > build cppdom 1.0.0 for win x64? Thanks. > > Doug > > > ------------------------------------------------------------------------------ > _______________________________________________ > Xml-cppdom-devel mailing list > Xml...@li... > https://lists.sourceforge.net/lists/listinfo/xml-cppdom-devel -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ |
|
From: Doug M. <mc...@ia...> - 2009-07-02 18:41:13
|
On Jul 2, 2009, at 12:43 PM, Patrick Hartling wrote: > x64 should do it, but it's been a long time since I last tried it. > > -Patrick > > On Jul 2, 2009, at 11:03 AM, Doug McCorkle wrote: > >> Hello, >> >> What is the appropriate architecture type to specify for scons to >> build cppdom 1.0.0 for win x64? Thanks. >> You are right in that it should work. I have tracked down the problem which is that python is not detecting that my parallels Win64 os is a win64 os. I am not sure what is getting messed up there. Any suggestions on how to make that work for python would be appreciated. Doug |
|
From: Doug M. <mc...@ia...> - 2009-07-03 14:37:31
|
On Jul 2, 2009, at 1:40 PM, Doug McCorkle wrote: > > On Jul 2, 2009, at 12:43 PM, Patrick Hartling wrote: > >> x64 should do it, but it's been a long time since I last tried it. >> >> -Patrick >> >> On Jul 2, 2009, at 11:03 AM, Doug McCorkle wrote: >> >>> Hello, >>> >>> What is the appropriate architecture type to specify for scons to >>> build cppdom 1.0.0 for win x64? Thanks. >>> > > You are right in that it should work. I have tracked down the problem > which is that python is not detecting that my parallels Win64 os is a > win64 os. I am not sure what is getting messed up there. Any > suggestions on how to make that work for python would be appreciated. For now I have hacked GetPlatform and GetArch to return the appropriate values for win64 builds but I am running into another problem. It appears that the EnvironmentBuilder is specifically configured for MSVS 8 which causes problems when trying to build with MSVS 9. Any thoughts on potential fixes? Can we use the default behaviour of SCons 1.2.0 for MSVS builds and not support older versions of SCons? Thanks. Doug |
|
From: Patrick H. <pa...@13...> - 2009-07-03 15:10:05
|
On Jul 3, 2009, at 9:37 AM, Doug McCorkle wrote: > > On Jul 2, 2009, at 1:40 PM, Doug McCorkle wrote: > >> >> On Jul 2, 2009, at 12:43 PM, Patrick Hartling wrote: >> >>> x64 should do it, but it's been a long time since I last tried it. >>> >>> -Patrick >>> >>> On Jul 2, 2009, at 11:03 AM, Doug McCorkle wrote: >>> >>>> Hello, >>>> >>>> What is the appropriate architecture type to specify for scons to >>>> build cppdom 1.0.0 for win x64? Thanks. >>>> >> >> You are right in that it should work. I have tracked down the problem >> which is that python is not detecting that my parallels Win64 os is a >> win64 os. I am not sure what is getting messed up there. Any >> suggestions on how to make that work for python would be appreciated. > > For now I have hacked GetPlatform and GetArch to return the > appropriate values for win64 builds but I am running into another > problem. It appears that the EnvironmentBuilder is specifically > configured for MSVS 8 which causes problems when trying to build with > MSVS 9. Any thoughts on potential fixes? Can we use the default > behaviour of SCons 1.2.0 for MSVS builds and not support older > versions of SCons? Thanks. Oh, right, I forgot about that mess. Give the new SCons support a try. If it works, the hacks for Win64 and Visual C++ 8.0 should be removed. I don't see any reason to support older versions of SCons, but then again, I don't have the final say on that. -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ |
|
From: Doug M. <mc...@ia...> - 2009-07-06 14:10:19
|
[snip] >> >> For now I have hacked GetPlatform and GetArch to return the >> appropriate values for win64 builds but I am running into another >> problem. It appears that the EnvironmentBuilder is specifically >> configured for MSVS 8 which causes problems when trying to build with >> MSVS 9. Any thoughts on potential fixes? Can we use the default >> behaviour of SCons 1.2.0 for MSVS builds and not support older >> versions of SCons? Thanks. > > > Oh, right, I forgot about that mess. Give the new SCons support a try. > If it works, the hacks for Win64 and Visual C++ 8.0 should be removed. > I don't see any reason to support older versions of SCons, but then > again, I don't have the final say on that. > Do you happen to know how build_env is initialized in the SConstruct? I see it exported and used but it never appears to be configured. Doug |
|
From: Patrick H. <pa...@13...> - 2009-07-07 14:41:56
Attachments:
signature.asc
|
Doug McCorkle wrote: > > [snip] > >>> >>> For now I have hacked GetPlatform and GetArch to return the >>> appropriate values for win64 builds but I am running into another >>> problem. It appears that the EnvironmentBuilder is specifically >>> configured for MSVS 8 which causes problems when trying to build with >>> MSVS 9. Any thoughts on potential fixes? Can we use the default >>> behaviour of SCons 1.2.0 for MSVS builds and not support older >>> versions of SCons? Thanks. >> >> >> Oh, right, I forgot about that mess. Give the new SCons support a try. >> If it works, the hacks for Win64 and Visual C++ 8.0 should be removed. >> I don't see any reason to support older versions of SCons, but then >> again, I don't have the final say on that. >> > > Do you happen to know how build_env is initialized in the SConstruct? I > see it exported and used but it never appears to be configured. Is it part of the Variants stuff? If not, then I don't know. -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ |
|
From: Doug M. <mc...@ia...> - 2009-07-07 14:51:35
|
On Jul 7, 2009, at 8:24 AM, Patrick Hartling wrote: > Doug McCorkle wrote: >> >> [snip] >> >>>> >>>> For now I have hacked GetPlatform and GetArch to return the >>>> appropriate values for win64 builds but I am running into another >>>> problem. It appears that the EnvironmentBuilder is specifically >>>> configured for MSVS 8 which causes problems when trying to build >>>> with >>>> MSVS 9. Any thoughts on potential fixes? Can we use the default >>>> behaviour of SCons 1.2.0 for MSVS builds and not support older >>>> versions of SCons? Thanks. >>> >>> >>> Oh, right, I forgot about that mess. Give the new SCons support a >>> try. >>> If it works, the hacks for Win64 and Visual C++ 8.0 should be >>> removed. >>> I don't see any reason to support older versions of SCons, but then >>> again, I don't have the final say on that. >>> >> >> Do you happen to know how build_env is initialized in the >> SConstruct? I >> see it exported and used but it never appears to be configured. > > Is it part of the Variants stuff? If not, then I don't know. I have something semi working with the latest point release of scons. Unfortunately, it seems like the variant stuff and the multiple environments floating around in sca is getting in the way of the new access to msvs in scons. I should have a more detailed report in a day or so. Doug |
|
From: Doug M. <mc...@ia...> - 2009-07-13 04:32:18
|
On Jul 7, 2009, at 9:51 AM, Doug McCorkle wrote: > > On Jul 7, 2009, at 8:24 AM, Patrick Hartling wrote: > >> Doug McCorkle wrote: >>> >>> [snip] >>> >>>>> >>>>> For now I have hacked GetPlatform and GetArch to return the >>>>> appropriate values for win64 builds but I am running into another >>>>> problem. It appears that the EnvironmentBuilder is specifically >>>>> configured for MSVS 8 which causes problems when trying to build >>>>> with >>>>> MSVS 9. Any thoughts on potential fixes? Can we use the default >>>>> behaviour of SCons 1.2.0 for MSVS builds and not support older >>>>> versions of SCons? Thanks. >>>> >>>> >>>> Oh, right, I forgot about that mess. Give the new SCons support a >>>> try. >>>> If it works, the hacks for Win64 and Visual C++ 8.0 should be >>>> removed. >>>> I don't see any reason to support older versions of SCons, but then >>>> again, I don't have the final say on that. >>>> >>> >>> Do you happen to know how build_env is initialized in the >>> SConstruct? I >>> see it exported and used but it never appears to be configured. >> >> Is it part of the Variants stuff? If not, then I don't know. > > I have something semi working with the latest point release of scons. > Unfortunately, it seems like the variant stuff and the multiple > environments floating around in sca is getting in the way of the new > access to msvs in scons. I should have a more detailed report in a day > or so. The issue is that the variables: MSVS_ARCH and MSVS_VERSION must be set before the Environment is created. When using variants this is done within the variant loop I believe. If the Environment is configured outside without using variants then things are a little more straight forward to correct. In general, the code that is in the msvs_misc function for the 64bit platform can be commented out. Also, there are problems with detecting whether the code is being run on a 64 bit platform. I have been unable to find a method that works other than to read registry values or environment variables. I found notes to this affect in the scons msvs common.py file as well. I think updating SCA to support msvc 8.0 and 9.0 for both 32 and 64 bit platforms would be fairly straight forward. Is it OK to require SCons 1.2.0 for SCA use? Doug |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X