No, we has using the old .bat with xpidl.exe

It was working until 16.
Is there some change in 17 that needs to use .py?

Anyway...
We have installed python, and running:
py D:\xpcom_info\xulrunner\sdk\bin\header.py --cachedir=D:\ -o 
D:\xpcom_info\Informatize\comp.h D:\xpcom_info\Informatize\comp.idl

Is giving us this error:
print getBuiltinOrNativeTypeName(self.params[0].realtype)

SyntaxError: invalid syntax

A ^ in the last "e" from getBuiltinOrNativeTypeName

:(


When we tryed to update to 17 and start having those errors, we started 
thinking that maybe we were doing something wrong from the beggining (like use 
the EXE), but all tuto's on internet are not updated...

Is there some tutorial that shows the correct way to create a extension, 
updated to version 17?

Thanks a lot!



Em quarta-feira, 28 de novembro de 2012 20h53min59s UTC-3, Simon Kornblith  
escreveu:
> Did you rebuild your automatically generated C++ headers using the
> 
> version of pyxpidl shipped with XULRunner 17? Details at
> 
> https://developer.mozilla.org/en-US/docs/XPIDL/pyxpidl
> 
> 
> 
> On Nov 28, 1:48 pm, Felipe Junges <felipejun...@gmail.com> wrote:
> 
> > Hi! First, sorry about my poor english =P
> 
> > I'm brazilian... so... I'll give my best =P
> 
> >
> 
> > Where I work, we have a Firefox add-on, what was working perfect until 
> > xulrunner 16, compiling in Visual Studio 2010.
> 
> >
> 
> > Now, we have updated it to xulrunner 17 and we are getting lots and lots of 
> > erros, when trying to compile.
> 
> > Like:
> 
> >
> 
> >   Code:
> 
> >     d:\xpcom_info\informatize\comp.h(25): error C2470: 'ISpecialThing' : 
> > looks like a function definition, but there is no parameter list; skipping 
> > apparent body
> 
> >     1>d:\xpcom_info\informatize\comp.h(38): error C2653: 'ISpecialThing' : 
> > is not a class or namespace name
> 
> >     1>d:\xpcom_info\informatize\comp.h(38): error C2143: syntax error : 
> > missing ';' before '<'
> 
> >     1>d:\xpcom_info\informatize\comp.h(38): error C2988: unrecognizable 
> > template declaration/definition
> 
> >     1>d:\xpcom_info\informatize\comp.h(38): error C2059: syntax error : '<'
> 
> >     >d:\xpcom_info\informatize\comp.h(38): error C2039: 'kIID' : is not a 
> > member of '`global namespace''
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(51): error C2989: 
> > 'nsAString' : class template has already been declared as a non-class 
> > template
> 
> >     1>          d:\xpcom_info\xulrunner\include\nsrootidl.h(18) : see 
> > declaration of 'nsAString'
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(52): error C2989: 
> > 'nsACString' : class template has already been declared as a non-class 
> > template
> 
> >     1>          d:\xpcom_info\xulrunner\include\nsrootidl.h(19) : see 
> > declaration of 'nsACString'
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(160): error C2332: 
> > 'enum' : missing tag name
> 
> >     d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(160): error C2989: 
> > '<unnamed-tag>' : class template has already been declared as a non-class 
> > template
> 
> >     1>          d:\xpcom_info\xulrunner\include\nsXPCOM.h(252) : see 
> > declaration of '<unnamed-tag>'
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(367): error C3861: 
> > 'NS_StringSetDataRange': identifier not found
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(392): error C3861: 
> > 'NS_StringSetDataRange': identifier not found
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(409): error C3861: 
> > 'NS_StringSetDataRange': identifier not found
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(465): error C2332: 
> > 'enum' : missing tag name
> 
> >     1>d:\xpcom_info\xulrunner\include\nsXPCOMStrings.h(465): error C2989: 
> > '<unnamed-tag>' : class template has already been declared as a non-class 
> > template
> 
> >
> 
> > And some more!
> 
> >
> 
> > We have made no changes in our code, when did the update.
> 
> > We have noticed that various errors are been reported in nsXPCOMStrings.h, 
> > the others are pointed in our code (that works perfect with xulrunner 16).
> 
> >
> 
> > It look like we have to put some "include" somewhere... Can anobody help us 
> > finding what did changed from 16 to 17, what does the programmers has to 
> > change?
> 
> > Our code is not much different from the XPCOM example:
> 
> >
> 
> > https://developer.mozilla.org/samples/x... m-test.zip
> 
> > That was explained here:https://developer.mozilla.org/en-US/doc... 
> > ual_Studio
> 
> >
> 
> > Ah! We have downloaded the example from this site and even we, gives the 
> > same erros in xulrunner 17.
> 
> >
> 
> > Thanks a lot!!!

_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to