You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Andy Grove <gr...@roguewave.com> on 2007/04/27 09:51:22 UTC
[C++] Unable to build Tuscany C++ with VS .NET 2003
I have read the instructions for building Tuscany C++ and have set up
paths to dependencies such as LIBXML2, ICONV, ZLIB etc.
I am using "Visual C++ .NET 2003 Standard Edition" on Windows XP SP2 and
I have run vcvars32.
However, when I run the build.bat it complains that it can't find a
"vcbuild" command. I have searched under program files and I do have a
vcbuild.dll but no batch file or exe by that name. I have also checked
that I have all VS .NET features installed.
Here is the full output:
C:\Development\apache-tuscany-cpp>build
using LIBXML2: C:\cpp\libxml2-2.6.23.win32
using ICONV: C:\cpp\iconv-1.9.1\windows\msvc7"
Setting environment for using Microsoft Visual Studio .NET 2003 tools.
(If you have another version of Visual Studio or Visual C++ installed
and wish
to use its tools from the command line, run vcvars32.bat for that
version.)
'vcbuild' is not recognized as an internal or external command,
operable program or batch file.
'vcbuild' is not recognized as an internal or external command,
operable program or batch file.
"AXIS2C_HOME not set: sdo_axiom will not be built"
Any help with this would be much appreciated.
Thanks,
Andy.
RE: [C++] Unable to build Tuscany C++ with VS .NET 2003
Posted by Andy Grove <gr...@roguewave.com>.
Thanks, Andrew (and Pete).
I've downloaded the express edition and now have it building.
Cheers,
Andy.
-----Original Message-----
From: Andrew Borley [mailto:ajborley@gmail.com]
Sent: 27 April 2007 10:07
To: tuscany-dev@ws.apache.org
Subject: Re: [C++] Unable to build Tuscany C++ with VS .NET 2003
Hi Andy,
If you're using the latest code or the M3 release candidate, we have
based the windows build on Visual C++ 2005 Express edition (for which
you will also need the MS Service 2005 Platform SDK - more
install/download info at [1]).
If you want to continue trying with VC++ 2003, you can try running a
Visual Studio command prompt, which should set up the command-line
environment. Or alternatively, you can open the .sln solution files (at
[2] for SDO and [3] for SCA) in the VS GUI and try compiling the
projects via that route.
Cheers
Andy
[1] http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/
[2]
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sdo/VSExpress/tusc
any_sdo/tuscany_sdo.sln
[3]
http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/VSExpress/tusc
any_sca/tuscany_sca.sln
On 4/27/07, Andy Grove <gr...@roguewave.com> wrote:
> I have read the instructions for building Tuscany C++ and have set up
> paths to dependencies such as LIBXML2, ICONV, ZLIB etc.
>
> I am using "Visual C++ .NET 2003 Standard Edition" on Windows XP SP2
> and I have run vcvars32.
>
> However, when I run the build.bat it complains that it can't find a
> "vcbuild" command. I have searched under program files and I do have a
> vcbuild.dll but no batch file or exe by that name. I have also checked
> that I have all VS .NET features installed.
>
> Here is the full output:
>
> C:\Development\apache-tuscany-cpp>build
> using LIBXML2: C:\cpp\libxml2-2.6.23.win32 using ICONV:
> C:\cpp\iconv-1.9.1\windows\msvc7"
> Setting environment for using Microsoft Visual Studio .NET 2003 tools.
> (If you have another version of Visual Studio or Visual C++ installed
> and wish to use its tools from the command line, run vcvars32.bat for
> that
> version.)
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> "AXIS2C_HOME not set: sdo_axiom will not be built"
>
> Any help with this would be much appreciated.
>
> Thanks,
>
> Andy.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [C++] Unable to build Tuscany C++ with VS .NET 2003
Posted by Andrew Borley <aj...@gmail.com>.
Hi Andy,
If you're using the latest code or the M3 release candidate, we have
based the windows build on Visual C++ 2005 Express edition (for which
you will also need the MS Service 2005 Platform SDK - more
install/download info at [1]).
If you want to continue trying with VC++ 2003, you can try running a
Visual Studio command prompt, which should set up the command-line
environment. Or alternatively, you can open the .sln solution files
(at [2] for SDO and [3] for SCA) in the VS GUI and try compiling the
projects via that route.
Cheers
Andy
[1] http://msdn.microsoft.com/vstudio/express/visualc/usingpsdk/
[2] http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sdo/VSExpress/tuscany_sdo/tuscany_sdo.sln
[3] http://svn.apache.org/repos/asf/incubator/tuscany/cpp/sca/VSExpress/tuscany_sca/tuscany_sca.sln
On 4/27/07, Andy Grove <gr...@roguewave.com> wrote:
> I have read the instructions for building Tuscany C++ and have set up
> paths to dependencies such as LIBXML2, ICONV, ZLIB etc.
>
> I am using "Visual C++ .NET 2003 Standard Edition" on Windows XP SP2 and
> I have run vcvars32.
>
> However, when I run the build.bat it complains that it can't find a
> "vcbuild" command. I have searched under program files and I do have a
> vcbuild.dll but no batch file or exe by that name. I have also checked
> that I have all VS .NET features installed.
>
> Here is the full output:
>
> C:\Development\apache-tuscany-cpp>build
> using LIBXML2: C:\cpp\libxml2-2.6.23.win32
> using ICONV: C:\cpp\iconv-1.9.1\windows\msvc7"
> Setting environment for using Microsoft Visual Studio .NET 2003 tools.
> (If you have another version of Visual Studio or Visual C++ installed
> and wish
> to use its tools from the command line, run vcvars32.bat for that
> version.)
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> "AXIS2C_HOME not set: sdo_axiom will not be built"
>
> Any help with this would be much appreciated.
>
> Thanks,
>
> Andy.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: [C++] Unable to build Tuscany C++ with VS .NET 2003
Posted by Pete Robbins <ro...@googlemail.com>.
Andy, we changed the build to use VC Express Edition as that is free. We no
longer have project files for earlier versions of VC. It was getting too
much to maintain.
Cheers,
On 27/04/07, Andy Grove <gr...@roguewave.com> wrote:
>
> I have read the instructions for building Tuscany C++ and have set up
> paths to dependencies such as LIBXML2, ICONV, ZLIB etc.
>
> I am using "Visual C++ .NET 2003 Standard Edition" on Windows XP SP2 and
> I have run vcvars32.
>
> However, when I run the build.bat it complains that it can't find a
> "vcbuild" command. I have searched under program files and I do have a
> vcbuild.dll but no batch file or exe by that name. I have also checked
> that I have all VS .NET features installed.
>
> Here is the full output:
>
> C:\Development\apache-tuscany-cpp>build
> using LIBXML2: C:\cpp\libxml2-2.6.23.win32
> using ICONV: C:\cpp\iconv-1.9.1\windows\msvc7"
> Setting environment for using Microsoft Visual Studio .NET 2003 tools.
> (If you have another version of Visual Studio or Visual C++ installed
> and wish
> to use its tools from the command line, run vcvars32.bat for that
> version.)
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> 'vcbuild' is not recognized as an internal or external command,
> operable program or batch file.
> "AXIS2C_HOME not set: sdo_axiom will not be built"
>
> Any help with this would be much appreciated.
>
> Thanks,
>
> Andy.
>
--
Pete