Re: [C++-sig] VC7 + auto_ptr + transfer of owership
auto_ptr support is only really complete in the current CVS version. There are some problems with it in 1.29.0.
Huhf, I'm afraid that I checkouted the yesterday's version, and that's the one that causes the problem ! Any idea ? Thanks, Nicolas _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
auto_ptr support is only really complete in the current CVS version. There are some problems with it in 1.29.0.
Huhf, I'm afraid that I checkouted the yesterday's version, and that's the one that causes the problem !
My fault ! I've fumbled my checkout !... sorry for the trouble. Thanks, Nicolas
Hi!!! I've have just checked-out boost from the CVS repository and I'm trying to build it with bjam for the first time. I'm using the Intel 6.0 compiler, along with the VC7 toolset. This is the command line I am using: bjam -sTOOLS=intel-win32 "-sINTEL_BASE_MSVC_TOOLSET=vc7" "-sVC7_ROOT=C:\Program Files\Microsoft Visual Studio .NET\VC7" "-sINTELC=C:\Program Files\Intel\Compiler60\IA32" "-sPYTHON_ROOT=c:\Bin\Python22" Despite of this, bjam is still trying to use the VC6 include path (that doesn't exist in my machine): -I"C:\Program Files\Microsoft Visual Studio\VC98\include" As expected, the icl isn't finding some basic include files (limits.h, utility, etc). Can you see anything wrong or missing in the command line I'm using? Is there any way to force bjam to add the correct VC7 include path? Thank you, Marcelo A. Camelo
"Marcelo A. Camelo" <camelo@esss.com.br> writes:
Hi!!!
I've have just checked-out boost from the CVS repository and I'm trying to build it with bjam for the first time.
I'm using the Intel 6.0 compiler, along with the VC7 toolset.
This is the command line I am using:
bjam -sTOOLS=intel-win32 "-sINTEL_BASE_MSVC_TOOLSET=vc7" "-sVC7_ROOT=C:\Program Files\Microsoft Visual Studio .NET\VC7" "-sINTELC=C:\Program Files\Intel\Compiler60\IA32" "-sPYTHON_ROOT=c:\Bin\Python22"
Despite of this, bjam is still trying to use the VC6 include path (that doesn't exist in my machine):
-I"C:\Program Files\Microsoft Visual Studio\VC98\include"
As expected, the icl isn't finding some basic include files (limits.h, utility, etc).
Can you see anything wrong or missing in the command line I'm using? Is there any way to force bjam to add the correct VC7 include path?
Is MSVCDir set in your environment? If so, it appears VC7_ROOT will be ignored. I think that's probably a mistake, but I don't want to try to change it this close to branching for a release. -- Dave Abrahams Boost Consulting www.boost-consulting.com
Is MSVCDir set in your environment?
Yep... pointing to the old VC6 dir...
If so, it appears VC7_ROOT will be ignored. I think that's probably a mistake, but I don't want to try to change it this close to branching for a release.
Unsetting %MSVCDir or setting it to the actual VC7 dir also didin't worked. In the first case, no include dir was passed to the compiler. In the second, the PlatformSDK include dir (were some of the standard VC7 header files are located) isn't passed. For the records: the solution I've adopted was setting the INCLUDE environment variable to the above mentioned directories. The INTEL compiler also uses the contents of this variable when searching for header files. The compilation works just fine now. Thank you for your prompt reply. Marcelo A. Camelo -----Original Message----- From: c++-sig-admin@python.org [mailto:c++-sig-admin@python.org] On Behalf Of David Abrahams Sent: segunda-feira, 24 de fevereiro de 2003 18:45 To: c++-sig@python.org Subject: Re: [C++-sig] Problem compiling with Intel/VC7 "Marcelo A. Camelo" <camelo@esss.com.br> writes:
Hi!!!
I've have just checked-out boost from the CVS repository and I'm trying to build it with bjam for the first time.
I'm using the Intel 6.0 compiler, along with the VC7 toolset.
This is the command line I am using:
bjam -sTOOLS=intel-win32 "-sINTEL_BASE_MSVC_TOOLSET=vc7" "-sVC7_ROOT=C:\Program Files\Microsoft Visual Studio .NET\VC7" "-sINTELC=C:\Program Files\Intel\Compiler60\IA32" "-sPYTHON_ROOT=c:\Bin\Python22"
Despite of this, bjam is still trying to use the VC6 include path (that doesn't exist in my machine):
-I"C:\Program Files\Microsoft Visual Studio\VC98\include"
As expected, the icl isn't finding some basic include files (limits.h, utility, etc).
Can you see anything wrong or missing in the command line I'm using? Is there any way to force bjam to add the correct VC7 include path?
Is MSVCDir set in your environment? If so, it appears VC7_ROOT will be ignored. I think that's probably a mistake, but I don't want to try to change it this close to branching for a release. -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ C++-sig mailing list C++-sig@python.org http://mail.python.org/mailman/listinfo/c++-sig
"Marcelo A. Camelo" <camelo@esss.com.br> writes:
Is MSVCDir set in your environment?
Yep... pointing to the old VC6 dir...
If so, it appears VC7_ROOT will be ignored. I think that's probably a mistake, but I don't want to try to change it this close to branching for a release.
Unsetting %MSVCDir or setting it to the actual VC7 dir also didin't worked. In the first case, no include dir was passed to the compiler.
Works for me. The compiler should invoke iccvars.bat before it runs, which should set up the INCLUDE environment variable. OTOH, if you installed your intel toolset to use the vc6 backend, that will point to the wrong place. We need to fix how this whole thing works, but I'd rather do it in BBv2, which is much more coherent.
In the second, the PlatformSDK include dir (were some of the standard VC7 header files are located) isn't passed.
Hm.
For the records: the solution I've adopted was setting the INCLUDE environment variable to the above mentioned directories. The INTEL compiler also uses the contents of this variable when searching for header files. The compilation works just fine now.
You're welcome. Sorry I don't have a better answer for today. -- Dave Abrahams Boost Consulting www.boost-consulting.com
"Marcelo A. Camelo" <camelo@esss.com.br> writes:
I've have just checked-out boost from the CVS repository and I'm trying to build it with bjam for the first time.
I'm using the Intel 6.0 compiler, along with the VC7 toolset.
This is the command line I am using:
bjam -sTOOLS=intel-win32 "-sINTEL_BASE_MSVC_TOOLSET=vc7" "-sVC7_ROOT=C:\Program Files\Microsoft Visual Studio .NET\VC7" "-sINTELC=C:\Program Files\Intel\Compiler60\IA32" "-sPYTHON_ROOT=c:\Bin\Python22"
Despite of this, bjam is still trying to use the VC6 include path (that doesn't exist in my machine):
-I"C:\Program Files\Microsoft Visual Studio\VC98\include"
Did you get past this problem, Marcelo? -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (3)
-
David Abrahams -
Marcelo A. Camelo -
Nicolas Lelong