You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2006/07/19 10:57:15 UTC
[jira] Commented: (AXISCPP-986) ANT Build failed
[ http://issues.apache.org/jira/browse/AXISCPP-986?page=comments#action_12422059 ]
Adrian Dick commented on AXISCPP-986:
-------------------------------------
Hi,
You don't mention which compiler you're using, but I know (from personal experience) that for Windows it should work fine with MS VC++ v6, v7 or v7.1 - hopefully later versions will work equally well, but it may be we need to make minor tweeks to the scripts.
But back to the specific problem, this sounds like you don't have Visual C++ set on the path before running the ant scripts. There is a script provided with MS VC++ to setup the environment at the command line (called vcvars32.bat for the version I'm currently using)
> ANT Build failed
> ----------------
>
> Key: AXISCPP-986
> URL: http://issues.apache.org/jira/browse/AXISCPP-986
> Project: Axis-C++
> Issue Type: Bug
> Components: Build - ANT
> Affects Versions: 1.6 Final
> Environment: Win XP
> Reporter: Manfred Pauli
>
> Hi!
> I tried to build Axis c++ for a new platform (windows mobile). But first I tried to build it for WinXP. But when executing the ant command, I get this errors:
> Buildfile: build.xml
> pre-init:
> set-platform-specifics:
> checkIfDebug:
> initialize:
> build:
> compile:
> compileClient:
> compileAxisClient:
> buildVersionResource:
> [delete] Deleting 1 files from C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Sourc
> e\build
> [copy] Copying 1 file to C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\bu
> ild
> BUILD FAILED
> C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\build.xml:245: The following err
> or occurred while executing this line:
> C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\build.xml:233: The following err
> or occurred while executing this line:
> C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\build.xml:96: The following erro
> r occurred while executing this line:
> C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\build\buildClient.xml:10: The fo
> llowing error occurred while executing this line:
> C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source\build.xml:82: Execute failed: ja
> va.io.IOException: CreateProcess: rc /fo "C:\Dokumente und Einstellungen\Manfred\Desktop\Ax
> is Source/build/version.res" "C:\Dokumente und Einstellungen\Manfred\Desktop\Axis Source/bu
> ild/version.temp.rc" error=2
> Total time: 2 seconds
> What's wrong here?
> Thanx for help!
> Greetings
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: javacode gen remnants
Posted by Nadir Amra <am...@us.ibm.com>.
I think we can re-introduce if need be. I do not think the current use
would benefit support for C++ namespaces and the method itself is very
simple.
Thanks.
Nadir K. Amra
Adrian Dick <ad...@uk.ibm.com> wrote on 07/19/2006 10:51:52 AM:
> Hi, Nadir,
>
> I'm all for simplification ... but just one thought....
> Is there anyway the getPackageName4QualifiedName.... methods could be
used
> to exploit C++ namespaces, as I know others have asked for in the past.
> That said, I suspect there would be quite a lot of work elsewhere to
> properly support this, so maybe it would make more sense to re-introduce
> the function when someone gets to implementing C++ namespaces.
>
> Adrian
> _______________________________________
> Adrian Dick (adrian.dick@uk.ibm.com)
>
> Nadir Amra <am...@us.ibm.com> wrote on 19/07/2006 15:18:52:
>
> > I plan on removing stuff that is related to the generation of java
code -
>
> > I assume this was just an oversight in not being removed previously.
For
> > example, in TypeMap we have java keywords array. And in WrapperUtils
we
> > have getPackegeName4QualifiedName....etc.
> >
> > Simplify, simplify, simplify :-)
> >
> > I plan on doing this in the next day or two so let me know if there
are
> > any objections.
> >
> > Nadir K. Amra
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: javacode gen remnants
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi, Nadir,
I'm all for simplification ... but just one thought....
Is there anyway the getPackageName4QualifiedName.... methods could be used
to exploit C++ namespaces, as I know others have asked for in the past.
That said, I suspect there would be quite a lot of work elsewhere to
properly support this, so maybe it would make more sense to re-introduce
the function when someone gets to implementing C++ namespaces.
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
Nadir Amra <am...@us.ibm.com> wrote on 19/07/2006 15:18:52:
> I plan on removing stuff that is related to the generation of java code -
> I assume this was just an oversight in not being removed previously. For
> example, in TypeMap we have java keywords array. And in WrapperUtils we
> have getPackegeName4QualifiedName....etc.
>
> Simplify, simplify, simplify :-)
>
> I plan on doing this in the next day or two so let me know if there are
> any objections.
>
> Nadir K. Amra
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
javacode gen remnants
Posted by Nadir Amra <am...@us.ibm.com>.
I plan on removing stuff that is related to the generation of java code -
I assume this was just an oversight in not being removed previously. For
example, in TypeMap we have java keywords array. And in WrapperUtils we
have getPackegeName4QualifiedName....etc.
Simplify, simplify, simplify :-)
I plan on doing this in the next day or two so let me know if there are
any objections.
Nadir K. Amra
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: TypeMap processing
Posted by John Hawkins <HA...@uk.ibm.com>.
As long as the test buckets works we're good to go :-)
Nadir Amra <am...@us.ibm.com>
21/07/2006 05:10
Please respond to
"Apache AXIS C Developers List" <ax...@ws.apache.org>
To
"Apache AXIS C Developers List" <ax...@ws.apache.org>
cc
Subject
TypeMap processing
I have changed and committed code so that one can tell whether to generate
a TypeMap entry by simply calling method isExternalized(). Basically by
default all types that are not anonymous types are externalized. To
externalize anonymous types another method is called. So there is no
place in the code where it looks for '>' in an object of class Type.
I have run the test buckets and things look good. One thing though. In
AllParamWriter.writeSource(), as it iterates through the TypeMap, the code
is as follows:
type = (Type) types.next();
if (type.isArray())
{ ... }
else if (type.isAnonymous() && !type.isExternalized())
{
if(WSDL2Ws.verbose)
System.out.println("ignoring anonymous type " +
type.getLanguageSpecificName() + "\n");
}
else
{
if (WSDL2Ws.verbose)
System.out.println("struct writer called
for......" + type.getName());
(new BeanParamWriter(wscontext, type)).writeSource();
(new ParmHeaderFileWriter(wscontext,
type)).writeSource();
}
I see no reason why I should not change the logic to:
if (!type.isExternalized())
{
if(WSDL2Ws.verbose)
System.out.println("ignoring anonymous type " +
type.getLanguageSpecificName() + "\n");
}
else if (type.isArray())
{ ... }
else
{
if (WSDL2Ws.verbose)
System.out.println("struct writer called
for......" + type.getName());
(new BeanParamWriter(wscontext, type)).writeSource();
(new ParmHeaderFileWriter(wscontext,
type)).writeSource();
}
And in fact I have changed it in code that I have and ran the test bucket
with no problems. I just want to make sure I am not missing something
before I commit it.
Nadir K. Amra
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
TypeMap processing
Posted by Nadir Amra <am...@us.ibm.com>.
I have changed and committed code so that one can tell whether to generate
a TypeMap entry by simply calling method isExternalized(). Basically by
default all types that are not anonymous types are externalized. To
externalize anonymous types another method is called. So there is no
place in the code where it looks for '>' in an object of class Type.
I have run the test buckets and things look good. One thing though. In
AllParamWriter.writeSource(), as it iterates through the TypeMap, the code
is as follows:
type = (Type) types.next();
if (type.isArray())
{ ... }
else if (type.isAnonymous() && !type.isExternalized())
{
if(WSDL2Ws.verbose)
System.out.println("ignoring anonymous type " +
type.getLanguageSpecificName() + "\n");
}
else
{
if (WSDL2Ws.verbose)
System.out.println("struct writer called
for......" + type.getName());
(new BeanParamWriter(wscontext, type)).writeSource();
(new ParmHeaderFileWriter(wscontext,
type)).writeSource();
}
I see no reason why I should not change the logic to:
if (!type.isExternalized())
{
if(WSDL2Ws.verbose)
System.out.println("ignoring anonymous type " +
type.getLanguageSpecificName() + "\n");
}
else if (type.isArray())
{ ... }
else
{
if (WSDL2Ws.verbose)
System.out.println("struct writer called
for......" + type.getName());
(new BeanParamWriter(wscontext, type)).writeSource();
(new ParmHeaderFileWriter(wscontext,
type)).writeSource();
}
And in fact I have changed it in code that I have and ran the test bucket
with no problems. I just want to make sure I am not missing something
before I commit it.
Nadir K. Amra
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org