Not managing to build .tlb for SimpleDOMNode.idl

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
This is amazingly frustrating. This doesn't make any sense.

I've installed the Vista SDK, I have Visual Studio 2005 installed, and I've
installed Visual Studio 2008 hoping this would somehow correct the problem.

I've copied every instance of objidl.idl that I could find within all three
packages, which is about 8 or 9 separate files, all of which are slightly
different from each other. I've tried every one of these when attempting to
compile ISimpleDOMNode.idl into a TLB class lib, and every time I get the
following error...

objidl.idl(35) : error MIDL2025 : syntax error : expecting an interface name
or DispatchInterfaceName or CoclassName or ModuleName or LibraryName or a
type specification near "if"
objidl.idl(36) : error MIDL2026 : cannot recover from earlier syntax errors;
aborting compilation

I'm using the commandline
midl ISimpleDOMNode.idl /tlb ISimpleDOMNode.tlb /nocpp /nologo
This being called after using CD to change the dir to that containing
midl.exe. I've also pasted all other supporting idl files that are needed
within the same folder to simplify the process.

This makes no sense. I've tried this on three separate computers with the
same results. The line number changes based on the objidl.idl file being
used, but it's always the same error.

I tried jumping down to the referenced line number (35) within objidl.idl
using a text editor, but it drops me into the end of the license info block,
which doesn't seem right either.

Does anyone know why this behavior is happening? I'm using XP Pro SP2, and
have all of the latest patches.

Any help would be appreciated.

Thanks,

Bryan



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand


----- Original Message -----
From: "Bryan Garaventa" <[hidden email]>
To: "Steve Lee" <[hidden email]>
Cc: "Aaron Leventhal" <[hidden email]>
Sent: Friday, July 18, 2008 9:58 AM
Subject: Re: Managed to build .tlb for SimpleDOMNode.idl


> Thanks, after installing the Vista SDK, I found the latest version of
> Midl.exe, which apparently is 7.
>
> I can successfully create all of the C++ headers without any errors.
>
> However, when I try to create a tlb using the commandline
>
> midl /nocpp /newtlb c:\idl\ISimpleDOMNode.idl
>
> I get the following message
>
> Microsoft (R) 32b/64b MIDL Compiler Version 7.00.0499
> Copyright (c) Microsoft Corporation 1991-2006. All rights reserved.
> Processing C:\idl\ISimpleDOMNode.idl
> Processing .\objidl.idl
> objidl.idl(35) : error MIDL2025 : syntax error : expecting an interface
> name
> or DispatchInterfaceName or CoclassName or ModuleName or LibraryName or a
> type specification near "if"
> objidl.idl(36) : error MIDL2026 : cannot recover from earlier syntax
> errors;
> aborting compilation
>
> I've attached the files that I copied over from the include folder within
> the SDK. There don't appear to be any others but these.
>
> Do these files match those that you are using? Specifically the
> objidl.idl?
>
> Thanks,
>
> Bryan
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
> ----- Original Message -----
> From: "Steve Lee" <[hidden email]>
> To: "Bryan Garaventa" <[hidden email]>
> Sent: Friday, July 18, 2008 3:02 AM
> Subject: Re: Managed to build .tlb for SimpleDOMNode.idl
>
>
>> 2008/7/17 Bryan Garaventa <[hidden email]>:
>>> Which dev environment are you using to compile when using MIDL.exe?
>>
>> I tried .NET 2003
>>
>>> Does the import references within the ISimpleDOMNode.idl need to be from
>>> a
>>> particular dev environment? I'm not too familiar with MIDL, but when
>>> searching about MIDL on the web, many of the answers lead to pages that
>>> no
>>> longer exist or to SDKs that no longer apply. It's weird. I'm likely
>>> missing
>>> something fairly obvious, but I'm a bit stumped.
>>
>> Bryan, did you run sdkvars.bar in the console? it sets up the PATH,
>> LIB &  INCLUDE  paths for all the tools.
>>
>> Steve Lee
>

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Steve Lee-3
Reposting to list

Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
build going and have run out of time to look more till next week :-(

One thing are you sure /nocpp is correct? Something may want the C pre
processor, which might be why it's barfing in the comments. Thats a
pretty basic syntax error indicating it really confused with the
source. I'm also not sure you need /tlb either.

You should check that INCLUDE is set correctly, it might not be using
the right files or your local copies.
Are you build in the MinGW environment or cmd? If you use
start-msvcN.bat it should be all set up for you (though I just had to
patch it for VC9Express)

Steve
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
Thanks, that's no problem.

I'm using cmd to access midl.exe, using the docs at
http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a reference.

Many of the included files appear to be spread around various directories
though, so it took me a while to track the errors enough to gather all of
these files into one main directory. This includes cl.exe and the other
referenced dll. So far, I've been using those files found in the Program
Files\Microsoft Visual Studio 8 folder. After installing VS9, I found two
objidl.idl files, one in the Smart Devices folder, and in the Smart Phone
folder, but I couldn't find any references to determine if these files are
device dependant. I'm not having much luck finding any docs that really
explain how Midl is supposed to be used, and which files are directly
relevant for a standard Win32 environment.

I did try the compilation without the /nocpp switch, and also leaving out
the /tlb switch as well. The results were weird. Apparently, the default
switches should automatically generate the C headers and the TLB within the
same directory. Well, the C headers appear to generate fine, no errors
appear within the command prompt during the compilation. This is using the
same objidl.idl file as mentioned before, located in the Program
Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However, no
TLB file is generated. Only when I disable the C processor using /no_cpp or
/nocpp, does this syntax error occur.

I'm hoping that I'm missing something simple, like not changing the correct
info in the ISimpleDOMNode.idl file, which would be a happy mistake since I
wouldn't believe I was actually going nuts.

Just in case, these are the lines I changed within the ISimpleDOMNode.idl
file based on Aaron's discovery earlier. (Changing all of the iDISP
constants from negative to positive values.)

const long DISPID_NODE_NODEINFO   = 5900;
const long DISPID_NODE_ATTRIBUTES = 5901;
const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
const long DISPID_NODE_COMPSTYLE  = 5903;
const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
const long DISPID_NODE_LANGUAGE = 5905;

Could this be the problem?

I appreciate the help, but it's no rush.

Best wishes,

Bryan



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand


----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Cc: "dev-accessibility Firefox" <[hidden email]>
Sent: Sunday, July 20, 2008 3:08 AM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Reposting to list
>
> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
> build going and have run out of time to look more till next week :-(
>
> One thing are you sure /nocpp is correct? Something may want the C pre
> processor, which might be why it's barfing in the comments. Thats a
> pretty basic syntax error indicating it really confused with the
> source. I'm also not sure you need /tlb either.
>
> You should check that INCLUDE is set correctly, it might not be using
> the right files or your local copies.
> Are you build in the MinGW environment or cmd? If you use
> start-msvcN.bat it should be all set up for you (though I just had to
> patch it for VC9Express)
>
> Steve

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
Actually, this output doesn't look like C++ header code, but rather an error
log from the midl compiler.

I've attached the generated files from midl.exe from the cmd prompt in case
anyone would like to take a look, and hopefully, can provide a totally
brilliant insight that can restore my faith in Microsoft products as a whole
in one fell swoop?

I can't say I understand it. This time I used the 2008 Vista SDK to make
sure I have the most recent files.

Also, I used the /I switch to designate the include folder, for instance
midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
ISimpleDOMNode.idl
So that none of the includes could be accidentally omitted.

I didn't get any errors in the command prompt, but in the .h file, it says
that I need a more recent version of rcndr.h and that I missing windows.h,
which is confusing. This is a 2008 update package so it should contain the
latest header files, I would assume anyway. Also, I checked the include
directory and it does contain a windows.h file in the same folder as
objidl.idl, so I'm not sure why it would be saying it's not there.

I wonder if MS has ever heard of the KISS principle...



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Bryan Garaventa" <[hidden email]>
To: "dev-accessibility Firefox" <[hidden email]>
Cc: "dev-accessibility Firefox" <[hidden email]>
Sent: Monday, July 21, 2008 1:24 PM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Thanks, that's no problem.
>
> I'm using cmd to access midl.exe, using the docs at
> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
> reference.
>
> Many of the included files appear to be spread around various directories
> though, so it took me a while to track the errors enough to gather all of
> these files into one main directory. This includes cl.exe and the other
> referenced dll. So far, I've been using those files found in the Program
> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found two
> objidl.idl files, one in the Smart Devices folder, and in the Smart Phone
> folder, but I couldn't find any references to determine if these files are
> device dependant. I'm not having much luck finding any docs that really
> explain how Midl is supposed to be used, and which files are directly
> relevant for a standard Win32 environment.
>
> I did try the compilation without the /nocpp switch, and also leaving out
> the /tlb switch as well. The results were weird. Apparently, the default
> switches should automatically generate the C headers and the TLB within
> the
> same directory. Well, the C headers appear to generate fine, no errors
> appear within the command prompt during the compilation. This is using the
> same objidl.idl file as mentioned before, located in the Program
> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However, no
> TLB file is generated. Only when I disable the C processor using /no_cpp
> or
> /nocpp, does this syntax error occur.
>
> I'm hoping that I'm missing something simple, like not changing the
> correct
> info in the ISimpleDOMNode.idl file, which would be a happy mistake since
> I
> wouldn't believe I was actually going nuts.
>
> Just in case, these are the lines I changed within the ISimpleDOMNode.idl
> file based on Aaron's discovery earlier. (Changing all of the iDISP
> constants from negative to positive values.)
>
> const long DISPID_NODE_NODEINFO   = 5900;
> const long DISPID_NODE_ATTRIBUTES = 5901;
> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
> const long DISPID_NODE_COMPSTYLE  = 5903;
> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
> const long DISPID_NODE_LANGUAGE = 5905;
>
> Could this be the problem?
>
> I appreciate the help, but it's no rush.
>
> Best wishes,
>
> Bryan
>
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
>
> ----- Original Message -----
> From: "Steve Lee" <[hidden email]>
> To: "Bryan Garaventa" <[hidden email]>
> Cc: "dev-accessibility Firefox" <[hidden email]>
> Sent: Sunday, July 20, 2008 3:08 AM
> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>
>
>> Reposting to list
>>
>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>> build going and have run out of time to look more till next week :-(
>>
>> One thing are you sure /nocpp is correct? Something may want the C pre
>> processor, which might be why it's barfing in the comments. Thats a
>> pretty basic syntax error indicating it really confused with the
>> source. I'm also not sure you need /tlb either.
>>
>> You should check that INCLUDE is set correctly, it might not be using
>> the right files or your local copies.
>> Are you build in the MinGW environment or cmd? If you use
>> start-msvcN.bat it should be all set up for you (though I just had to
>> patch it for VC9Express)
>>
>> Steve
>
> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility 

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Steve Lee-3
Sorry If I didn't make it clear but you should run a batch file called
something like vcvars.bat in you command prompt first. This will set
up the environment variable so the compilers find the correct files.
This sounds like the proble. You should nto have to copy files and
that can cause confusion due to the way the compiler searches for
included files. The exact file name various with the version of the
tools you use. The only complication comes as you often have set
things up for both the VC and SDK.

If you use the Mozilla Build system it should sort this out for you
and gives you a nice UNIX like shell.

Steve

2008/7/22 Bryan Garaventa <[hidden email]>:

> Actually, this output doesn't look like C++ header code, but rather an error
> log from the midl compiler.
>
> I've attached the generated files from midl.exe from the cmd prompt in case
> anyone would like to take a look, and hopefully, can provide a totally
> brilliant insight that can restore my faith in Microsoft products as a whole
> in one fell swoop?
>
> I can't say I understand it. This time I used the 2008 Vista SDK to make
> sure I have the most recent files.
>
> Also, I used the /I switch to designate the include folder, for instance
> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
> ISimpleDOMNode.idl
> So that none of the includes could be accidentally omitted.
>
> I didn't get any errors in the command prompt, but in the .h file, it says
> that I need a more recent version of rcndr.h and that I missing windows.h,
> which is confusing. This is a 2008 update package so it should contain the
> latest header files, I would assume anyway. Also, I checked the include
> directory and it does contain a windows.h file in the same folder as
> objidl.idl, so I'm not sure why it would be saying it's not there.
>
> I wonder if MS has ever heard of the KISS principle...
>
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
> ----- Original Message ----- From: "Bryan Garaventa"
> <[hidden email]>
> To: "dev-accessibility Firefox" <[hidden email]>
> Cc: "dev-accessibility Firefox" <[hidden email]>
> Sent: Monday, July 21, 2008 1:24 PM
> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>
>
>> Thanks, that's no problem.
>>
>> I'm using cmd to access midl.exe, using the docs at
>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>> reference.
>>
>> Many of the included files appear to be spread around various directories
>> though, so it took me a while to track the errors enough to gather all of
>> these files into one main directory. This includes cl.exe and the other
>> referenced dll. So far, I've been using those files found in the Program
>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found two
>> objidl.idl files, one in the Smart Devices folder, and in the Smart Phone
>> folder, but I couldn't find any references to determine if these files are
>> device dependant. I'm not having much luck finding any docs that really
>> explain how Midl is supposed to be used, and which files are directly
>> relevant for a standard Win32 environment.
>>
>> I did try the compilation without the /nocpp switch, and also leaving out
>> the /tlb switch as well. The results were weird. Apparently, the default
>> switches should automatically generate the C headers and the TLB within
>> the
>> same directory. Well, the C headers appear to generate fine, no errors
>> appear within the command prompt during the compilation. This is using the
>> same objidl.idl file as mentioned before, located in the Program
>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However, no
>> TLB file is generated. Only when I disable the C processor using /no_cpp
>> or
>> /nocpp, does this syntax error occur.
>>
>> I'm hoping that I'm missing something simple, like not changing the
>> correct
>> info in the ISimpleDOMNode.idl file, which would be a happy mistake since
>> I
>> wouldn't believe I was actually going nuts.
>>
>> Just in case, these are the lines I changed within the ISimpleDOMNode.idl
>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>> constants from negative to positive values.)
>>
>> const long DISPID_NODE_NODEINFO   = 5900;
>> const long DISPID_NODE_ATTRIBUTES = 5901;
>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>> const long DISPID_NODE_COMPSTYLE  = 5903;
>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>> const long DISPID_NODE_LANGUAGE = 5905;
>>
>> Could this be the problem?
>>
>> I appreciate the help, but it's no rush.
>>
>> Best wishes,
>>
>> Bryan
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>>
>> ----- Original Message ----- From: "Steve Lee" <[hidden email]>
>> To: "Bryan Garaventa" <[hidden email]>
>> Cc: "dev-accessibility Firefox" <[hidden email]>
>> Sent: Sunday, July 20, 2008 3:08 AM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>> Reposting to list
>>>
>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>> build going and have run out of time to look more till next week :-(
>>>
>>> One thing are you sure /nocpp is correct? Something may want the C pre
>>> processor, which might be why it's barfing in the comments. Thats a
>>> pretty basic syntax error indicating it really confused with the
>>> source. I'm also not sure you need /tlb either.
>>>
>>> You should check that INCLUDE is set correctly, it might not be using
>>> the right files or your local copies.
>>> Are you build in the MinGW environment or cmd? If you use
>>> start-msvcN.bat it should be all set up for you (though I just had to
>>> patch it for VC9Express)
>>>
>>> Steve
>>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>
> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility
>
>



--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
Thanks, sadly it gives me the same behavior.

These were my steps...
1) I went to
C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not really sure
if any of this made a difference or not really.)
4) From Start > Programs > Microsoft Visual Studio 2008 > Visual Studio
Tools , I opened Visual Studio 2008 Command Prompt.
5) Ran vcvarsall.bat to set up the rest of the variables.
6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
midl ISimpleDOMNode.idl

I've attached the only generated files. This includes the ISimpleDOMNode.idl
file for reference. No TLB, just .c files.

Would it be possible for me to just create a C++ project in VS.net using
these C files to make my own class lib? This shouldn't be necessary, but I
don't know what else to try.

Arg,

Bryan



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Cc: "dev-accessibility Firefox" <[hidden email]>
Sent: Monday, July 21, 2008 11:09 PM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Sorry If I didn't make it clear but you should run a batch file called
> something like vcvars.bat in you command prompt first. This will set
> up the environment variable so the compilers find the correct files.
> This sounds like the proble. You should nto have to copy files and
> that can cause confusion due to the way the compiler searches for
> included files. The exact file name various with the version of the
> tools you use. The only complication comes as you often have set
> things up for both the VC and SDK.
>
> If you use the Mozilla Build system it should sort this out for you
> and gives you a nice UNIX like shell.
>
> Steve
>
> 2008/7/22 Bryan Garaventa <[hidden email]>:
>> Actually, this output doesn't look like C++ header code, but rather an
>> error
>> log from the midl compiler.
>>
>> I've attached the generated files from midl.exe from the cmd prompt in
>> case
>> anyone would like to take a look, and hopefully, can provide a totally
>> brilliant insight that can restore my faith in Microsoft products as a
>> whole
>> in one fell swoop?
>>
>> I can't say I understand it. This time I used the 2008 Vista SDK to make
>> sure I have the most recent files.
>>
>> Also, I used the /I switch to designate the include folder, for instance
>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>> ISimpleDOMNode.idl
>> So that none of the includes could be accidentally omitted.
>>
>> I didn't get any errors in the command prompt, but in the .h file, it
>> says
>> that I need a more recent version of rcndr.h and that I missing
>> windows.h,
>> which is confusing. This is a 2008 update package so it should contain
>> the
>> latest header files, I would assume anyway. Also, I checked the include
>> directory and it does contain a windows.h file in the same folder as
>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>
>> I wonder if MS has ever heard of the KISS principle...
>>
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>> ----- Original Message ----- From: "Bryan Garaventa"
>> <[hidden email]>
>> To: "dev-accessibility Firefox" <[hidden email]>
>> Cc: "dev-accessibility Firefox" <[hidden email]>
>> Sent: Monday, July 21, 2008 1:24 PM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>> Thanks, that's no problem.
>>>
>>> I'm using cmd to access midl.exe, using the docs at
>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>> reference.
>>>
>>> Many of the included files appear to be spread around various
>>> directories
>>> though, so it took me a while to track the errors enough to gather all
>>> of
>>> these files into one main directory. This includes cl.exe and the other
>>> referenced dll. So far, I've been using those files found in the Program
>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found
>>> two
>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>> Phone
>>> folder, but I couldn't find any references to determine if these files
>>> are
>>> device dependant. I'm not having much luck finding any docs that really
>>> explain how Midl is supposed to be used, and which files are directly
>>> relevant for a standard Win32 environment.
>>>
>>> I did try the compilation without the /nocpp switch, and also leaving
>>> out
>>> the /tlb switch as well. The results were weird. Apparently, the default
>>> switches should automatically generate the C headers and the TLB within
>>> the
>>> same directory. Well, the C headers appear to generate fine, no errors
>>> appear within the command prompt during the compilation. This is using
>>> the
>>> same objidl.idl file as mentioned before, located in the Program
>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However,
>>> no
>>> TLB file is generated. Only when I disable the C processor using /no_cpp
>>> or
>>> /nocpp, does this syntax error occur.
>>>
>>> I'm hoping that I'm missing something simple, like not changing the
>>> correct
>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>> since
>>> I
>>> wouldn't believe I was actually going nuts.
>>>
>>> Just in case, these are the lines I changed within the
>>> ISimpleDOMNode.idl
>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>> constants from negative to positive values.)
>>>
>>> const long DISPID_NODE_NODEINFO   = 5900;
>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>
>>> Could this be the problem?
>>>
>>> I appreciate the help, but it's no rush.
>>>
>>> Best wishes,
>>>
>>> Bryan
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> Bryan Garaventa
>>> Senior Accessibility Engineer
>>> SSB + BART Group
>>> [hidden email]
>>> www.SSBBartGroup.com
>>> Accessibility-On-Demand
>>>
>>>
>>> ----- Original Message ----- From: "Steve Lee" <[hidden email]>
>>> To: "Bryan Garaventa" <[hidden email]>
>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>> Sent: Sunday, July 20, 2008 3:08 AM
>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>
>>>
>>>> Reposting to list
>>>>
>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>>> build going and have run out of time to look more till next week :-(
>>>>
>>>> One thing are you sure /nocpp is correct? Something may want the C pre
>>>> processor, which might be why it's barfing in the comments. Thats a
>>>> pretty basic syntax error indicating it really confused with the
>>>> source. I'm also not sure you need /tlb either.
>>>>
>>>> You should check that INCLUDE is set correctly, it might not be using
>>>> the right files or your local copies.
>>>> Are you build in the MinGW environment or cmd? If you use
>>>> start-msvcN.bat it should be all set up for you (though I just had to
>>>> patch it for VC9Express)
>>>>
>>>> Steve
>>>
>>> _______________________________________________
>>> dev-accessibility mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>>
>
>
>
> --
> Steve Lee
> Open Source Assistive Technology Software and Accessibility
> fullmeasure.co.uk

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
I guess attachments don't work for the list. As an alt I've uploaded the zip
to
http://gutterstar.net/ISimpleDOMNode.zip

This contains the files
ISimpleDOMNode.idl
dlldata.c
ISimpleDOMNode.h
ISimpleDOMNode_i.c
ISimpleDOMNode_p.c

Other than ISimpleDOMNode.idl, these other files are all that the midl
compiler will generate.


--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Bryan Garaventa" <[hidden email]>
To: "dev-accessibility Firefox" <[hidden email]>
Sent: Tuesday, July 22, 2008 10:59 AM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Thanks, sadly it gives me the same behavior.
>
> These were my steps...
> 1) I went to
> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not really
> sure
> if any of this made a difference or not really.)
> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual Studio
> Tools , I opened Visual Studio 2008 Command Prompt.
> 5) Ran vcvarsall.bat to set up the rest of the variables.
> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
> midl ISimpleDOMNode.idl
>
> I've attached the only generated files. This includes the
> ISimpleDOMNode.idl
> file for reference. No TLB, just .c files.
>
> Would it be possible for me to just create a C++ project in VS.net using
> these C files to make my own class lib? This shouldn't be necessary, but I
> don't know what else to try.
>
> Arg,
>
> Bryan
>
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
> ----- Original Message -----
> From: "Steve Lee" <[hidden email]>
> To: "Bryan Garaventa" <[hidden email]>
> Cc: "dev-accessibility Firefox" <[hidden email]>
> Sent: Monday, July 21, 2008 11:09 PM
> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>
>
>> Sorry If I didn't make it clear but you should run a batch file called
>> something like vcvars.bat in you command prompt first. This will set
>> up the environment variable so the compilers find the correct files.
>> This sounds like the proble. You should nto have to copy files and
>> that can cause confusion due to the way the compiler searches for
>> included files. The exact file name various with the version of the
>> tools you use. The only complication comes as you often have set
>> things up for both the VC and SDK.
>>
>> If you use the Mozilla Build system it should sort this out for you
>> and gives you a nice UNIX like shell.
>>
>> Steve
>>
>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>> Actually, this output doesn't look like C++ header code, but rather an
>>> error
>>> log from the midl compiler.
>>>
>>> I've attached the generated files from midl.exe from the cmd prompt in
>>> case
>>> anyone would like to take a look, and hopefully, can provide a totally
>>> brilliant insight that can restore my faith in Microsoft products as a
>>> whole
>>> in one fell swoop?
>>>
>>> I can't say I understand it. This time I used the 2008 Vista SDK to make
>>> sure I have the most recent files.
>>>
>>> Also, I used the /I switch to designate the include folder, for instance
>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>> ISimpleDOMNode.idl
>>> So that none of the includes could be accidentally omitted.
>>>
>>> I didn't get any errors in the command prompt, but in the .h file, it
>>> says
>>> that I need a more recent version of rcndr.h and that I missing
>>> windows.h,
>>> which is confusing. This is a 2008 update package so it should contain
>>> the
>>> latest header files, I would assume anyway. Also, I checked the include
>>> directory and it does contain a windows.h file in the same folder as
>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>
>>> I wonder if MS has ever heard of the KISS principle...
>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> Bryan Garaventa
>>> Senior Accessibility Engineer
>>> SSB + BART Group
>>> [hidden email]
>>> www.SSBBartGroup.com
>>> Accessibility-On-Demand
>>>
>>> ----- Original Message ----- From: "Bryan Garaventa"
>>> <[hidden email]>
>>> To: "dev-accessibility Firefox" <[hidden email]>
>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>> Sent: Monday, July 21, 2008 1:24 PM
>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>
>>>
>>>> Thanks, that's no problem.
>>>>
>>>> I'm using cmd to access midl.exe, using the docs at
>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>> reference.
>>>>
>>>> Many of the included files appear to be spread around various
>>>> directories
>>>> though, so it took me a while to track the errors enough to gather all
>>>> of
>>>> these files into one main directory. This includes cl.exe and the other
>>>> referenced dll. So far, I've been using those files found in the
>>>> Program
>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found
>>>> two
>>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>>> Phone
>>>> folder, but I couldn't find any references to determine if these files
>>>> are
>>>> device dependant. I'm not having much luck finding any docs that really
>>>> explain how Midl is supposed to be used, and which files are directly
>>>> relevant for a standard Win32 environment.
>>>>
>>>> I did try the compilation without the /nocpp switch, and also leaving
>>>> out
>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>> default
>>>> switches should automatically generate the C headers and the TLB within
>>>> the
>>>> same directory. Well, the C headers appear to generate fine, no errors
>>>> appear within the command prompt during the compilation. This is using
>>>> the
>>>> same objidl.idl file as mentioned before, located in the Program
>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However,
>>>> no
>>>> TLB file is generated. Only when I disable the C processor using
>>>> /no_cpp
>>>> or
>>>> /nocpp, does this syntax error occur.
>>>>
>>>> I'm hoping that I'm missing something simple, like not changing the
>>>> correct
>>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>>> since
>>>> I
>>>> wouldn't believe I was actually going nuts.
>>>>
>>>> Just in case, these are the lines I changed within the
>>>> ISimpleDOMNode.idl
>>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>>> constants from negative to positive values.)
>>>>
>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>
>>>> Could this be the problem?
>>>>
>>>> I appreciate the help, but it's no rush.
>>>>
>>>> Best wishes,
>>>>
>>>> Bryan
>>>>
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Bryan Garaventa
>>>> Senior Accessibility Engineer
>>>> SSB + BART Group
>>>> [hidden email]
>>>> www.SSBBartGroup.com
>>>> Accessibility-On-Demand
>>>>
>>>>
>>>> ----- Original Message ----- From: "Steve Lee"
>>>> <[hidden email]>
>>>> To: "Bryan Garaventa" <[hidden email]>
>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>
>>>>
>>>>> Reposting to list
>>>>>
>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>>>> build going and have run out of time to look more till next week :-(
>>>>>
>>>>> One thing are you sure /nocpp is correct? Something may want the C pre
>>>>> processor, which might be why it's barfing in the comments. Thats a
>>>>> pretty basic syntax error indicating it really confused with the
>>>>> source. I'm also not sure you need /tlb either.
>>>>>
>>>>> You should check that INCLUDE is set correctly, it might not be using
>>>>> the right files or your local copies.
>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>> start-msvcN.bat it should be all set up for you (though I just had to
>>>>> patch it for VC9Express)
>>>>>
>>>>> Steve
>>>>
>>>> _______________________________________________
>>>> dev-accessibility mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>
>>> _______________________________________________
>>> dev-accessibility mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>
>>>
>>
>>
>>
>> --
>> Steve Lee
>> Open Source Assistive Technology Software and Accessibility
>> fullmeasure.co.uk
>


--------------------------------------------------------------------------------


> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility
>

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Steve Lee-3
Bryan, I'm just stepping back from this and thinking that if you are
really trying to add to a files that already exists in the Mozilla
source tree the best solution is to use mozilla build to build the
original and then chat to the guys working on that area on IRC in
#a11y if you still have problems.

Perhaps that will give you a less frustrating time as I know how
depressing it can be getting a build env up with MS tools as there are
many configs and options and interactions. Timing may be a small issue
as I think the devs are in China.

Just an idea

Cheers

Steve

2008/7/22 Bryan Garaventa <[hidden email]>:

> I guess attachments don't work for the list. As an alt I've uploaded the zip
> to
> http://gutterstar.net/ISimpleDOMNode.zip
>
> This contains the files
> ISimpleDOMNode.idl
> dlldata.c
> ISimpleDOMNode.h
> ISimpleDOMNode_i.c
> ISimpleDOMNode_p.c
>
> Other than ISimpleDOMNode.idl, these other files are all that the midl
> compiler will generate.
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
> ----- Original Message -----
> From: "Bryan Garaventa" <[hidden email]>
> To: "dev-accessibility Firefox" <[hidden email]>
> Sent: Tuesday, July 22, 2008 10:59 AM
> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>
>
>> Thanks, sadly it gives me the same behavior.
>>
>> These were my steps...
>> 1) I went to
>> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
>> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
>> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not really
>> sure
>> if any of this made a difference or not really.)
>> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual Studio
>> Tools , I opened Visual Studio 2008 Command Prompt.
>> 5) Ran vcvarsall.bat to set up the rest of the variables.
>> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
>> midl ISimpleDOMNode.idl
>>
>> I've attached the only generated files. This includes the
>> ISimpleDOMNode.idl
>> file for reference. No TLB, just .c files.
>>
>> Would it be possible for me to just create a C++ project in VS.net using
>> these C files to make my own class lib? This shouldn't be necessary, but I
>> don't know what else to try.
>>
>> Arg,
>>
>> Bryan
>>
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>> ----- Original Message -----
>> From: "Steve Lee" <[hidden email]>
>> To: "Bryan Garaventa" <[hidden email]>
>> Cc: "dev-accessibility Firefox" <[hidden email]>
>> Sent: Monday, July 21, 2008 11:09 PM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>> Sorry If I didn't make it clear but you should run a batch file called
>>> something like vcvars.bat in you command prompt first. This will set
>>> up the environment variable so the compilers find the correct files.
>>> This sounds like the proble. You should nto have to copy files and
>>> that can cause confusion due to the way the compiler searches for
>>> included files. The exact file name various with the version of the
>>> tools you use. The only complication comes as you often have set
>>> things up for both the VC and SDK.
>>>
>>> If you use the Mozilla Build system it should sort this out for you
>>> and gives you a nice UNIX like shell.
>>>
>>> Steve
>>>
>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>> Actually, this output doesn't look like C++ header code, but rather an
>>>> error
>>>> log from the midl compiler.
>>>>
>>>> I've attached the generated files from midl.exe from the cmd prompt in
>>>> case
>>>> anyone would like to take a look, and hopefully, can provide a totally
>>>> brilliant insight that can restore my faith in Microsoft products as a
>>>> whole
>>>> in one fell swoop?
>>>>
>>>> I can't say I understand it. This time I used the 2008 Vista SDK to make
>>>> sure I have the most recent files.
>>>>
>>>> Also, I used the /I switch to designate the include folder, for instance
>>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>>> ISimpleDOMNode.idl
>>>> So that none of the includes could be accidentally omitted.
>>>>
>>>> I didn't get any errors in the command prompt, but in the .h file, it
>>>> says
>>>> that I need a more recent version of rcndr.h and that I missing
>>>> windows.h,
>>>> which is confusing. This is a 2008 update package so it should contain
>>>> the
>>>> latest header files, I would assume anyway. Also, I checked the include
>>>> directory and it does contain a windows.h file in the same folder as
>>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>>
>>>> I wonder if MS has ever heard of the KISS principle...
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Bryan Garaventa
>>>> Senior Accessibility Engineer
>>>> SSB + BART Group
>>>> [hidden email]
>>>> www.SSBBartGroup.com
>>>> Accessibility-On-Demand
>>>>
>>>> ----- Original Message ----- From: "Bryan Garaventa"
>>>> <[hidden email]>
>>>> To: "dev-accessibility Firefox" <[hidden email]>
>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>> Sent: Monday, July 21, 2008 1:24 PM
>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>
>>>>
>>>>> Thanks, that's no problem.
>>>>>
>>>>> I'm using cmd to access midl.exe, using the docs at
>>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>>> reference.
>>>>>
>>>>> Many of the included files appear to be spread around various
>>>>> directories
>>>>> though, so it took me a while to track the errors enough to gather all
>>>>> of
>>>>> these files into one main directory. This includes cl.exe and the other
>>>>> referenced dll. So far, I've been using those files found in the
>>>>> Program
>>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found
>>>>> two
>>>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>>>> Phone
>>>>> folder, but I couldn't find any references to determine if these files
>>>>> are
>>>>> device dependant. I'm not having much luck finding any docs that really
>>>>> explain how Midl is supposed to be used, and which files are directly
>>>>> relevant for a standard Win32 environment.
>>>>>
>>>>> I did try the compilation without the /nocpp switch, and also leaving
>>>>> out
>>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>>> default
>>>>> switches should automatically generate the C headers and the TLB within
>>>>> the
>>>>> same directory. Well, the C headers appear to generate fine, no errors
>>>>> appear within the command prompt during the compilation. This is using
>>>>> the
>>>>> same objidl.idl file as mentioned before, located in the Program
>>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder. However,
>>>>> no
>>>>> TLB file is generated. Only when I disable the C processor using
>>>>> /no_cpp
>>>>> or
>>>>> /nocpp, does this syntax error occur.
>>>>>
>>>>> I'm hoping that I'm missing something simple, like not changing the
>>>>> correct
>>>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>>>> since
>>>>> I
>>>>> wouldn't believe I was actually going nuts.
>>>>>
>>>>> Just in case, these are the lines I changed within the
>>>>> ISimpleDOMNode.idl
>>>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>>>> constants from negative to positive values.)
>>>>>
>>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>>
>>>>> Could this be the problem?
>>>>>
>>>>> I appreciate the help, but it's no rush.
>>>>>
>>>>> Best wishes,
>>>>>
>>>>> Bryan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------
>>>>> Bryan Garaventa
>>>>> Senior Accessibility Engineer
>>>>> SSB + BART Group
>>>>> [hidden email]
>>>>> www.SSBBartGroup.com
>>>>> Accessibility-On-Demand
>>>>>
>>>>>
>>>>> ----- Original Message ----- From: "Steve Lee"
>>>>> <[hidden email]>
>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>
>>>>>
>>>>>> Reposting to list
>>>>>>
>>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>>>>> build going and have run out of time to look more till next week :-(
>>>>>>
>>>>>> One thing are you sure /nocpp is correct? Something may want the C pre
>>>>>> processor, which might be why it's barfing in the comments. Thats a
>>>>>> pretty basic syntax error indicating it really confused with the
>>>>>> source. I'm also not sure you need /tlb either.
>>>>>>
>>>>>> You should check that INCLUDE is set correctly, it might not be using
>>>>>> the right files or your local copies.
>>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>>> start-msvcN.bat it should be all set up for you (though I just had to
>>>>>> patch it for VC9Express)
>>>>>>
>>>>>> Steve
>>>>>
>>>>> _______________________________________________
>>>>> dev-accessibility mailing list
>>>>> [hidden email]
>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>
>>>> _______________________________________________
>>>> dev-accessibility mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Steve Lee
>>> Open Source Assistive Technology Software and Accessibility
>>> fullmeasure.co.uk
>>
>
>
> --------------------------------------------------------------------------------
>
>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>
> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility
>



--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
That's alright, I understand. What I'm trying to do is amazingly simple, and
that's where all of my frustration comes into it.

I just need the compiled ISimpleDOMNode.tlb class lib file. It doesn't
matter where it comes from, all that is needed is if the environment switch
is set for Win32, this would do the trick.

I'm building an ActiveX control, and need to use the ISimpleDOMNode.tlb as a
reference in order for it to work properly.

If anyone can successfully compile the ISimpleDOMNode.tlb and just send it
to me as an attachment, that would solve everything. I have no idea why it
isn't working for me, but it sounds like everyone except me can accomplish
it successfully. I've written about the Midl compiler issue in the MSDN
forums, but haven't received any reply as yet.

This missing class lib file is my proverbial wrench in the gears, the lack
of it is stopping any progress.

The reason why I haven't compiled Mozilla is that I'm not really sure how.
It doesn't sound like this would solve the problem though, since I would
still need the ISimpleDOMNode.tlb class lib file. Is this class lib
automatically created when Mozilla is compiled? Can I find this in my
current installation of Mozilla?

It's all a bit discouraging... How something so small can be such a large
problem.



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Cc: "dev-accessibility Firefox" <[hidden email]>
Sent: Wednesday, July 23, 2008 1:54 AM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Bryan, I'm just stepping back from this and thinking that if you are
> really trying to add to a files that already exists in the Mozilla
> source tree the best solution is to use mozilla build to build the
> original and then chat to the guys working on that area on IRC in
> #a11y if you still have problems.
>
> Perhaps that will give you a less frustrating time as I know how
> depressing it can be getting a build env up with MS tools as there are
> many configs and options and interactions. Timing may be a small issue
> as I think the devs are in China.
>
> Just an idea
>
> Cheers
>
> Steve
>
> 2008/7/22 Bryan Garaventa <[hidden email]>:
>> I guess attachments don't work for the list. As an alt I've uploaded the
>> zip
>> to
>> http://gutterstar.net/ISimpleDOMNode.zip
>>
>> This contains the files
>> ISimpleDOMNode.idl
>> dlldata.c
>> ISimpleDOMNode.h
>> ISimpleDOMNode_i.c
>> ISimpleDOMNode_p.c
>>
>> Other than ISimpleDOMNode.idl, these other files are all that the midl
>> compiler will generate.
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>> ----- Original Message -----
>> From: "Bryan Garaventa" <[hidden email]>
>> To: "dev-accessibility Firefox" <[hidden email]>
>> Sent: Tuesday, July 22, 2008 10:59 AM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>> Thanks, sadly it gives me the same behavior.
>>>
>>> These were my steps...
>>> 1) I went to
>>> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
>>> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
>>> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not really
>>> sure
>>> if any of this made a difference or not really.)
>>> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual Studio
>>> Tools , I opened Visual Studio 2008 Command Prompt.
>>> 5) Ran vcvarsall.bat to set up the rest of the variables.
>>> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
>>> midl ISimpleDOMNode.idl
>>>
>>> I've attached the only generated files. This includes the
>>> ISimpleDOMNode.idl
>>> file for reference. No TLB, just .c files.
>>>
>>> Would it be possible for me to just create a C++ project in VS.net using
>>> these C files to make my own class lib? This shouldn't be necessary, but
>>> I
>>> don't know what else to try.
>>>
>>> Arg,
>>>
>>> Bryan
>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> Bryan Garaventa
>>> Senior Accessibility Engineer
>>> SSB + BART Group
>>> [hidden email]
>>> www.SSBBartGroup.com
>>> Accessibility-On-Demand
>>>
>>> ----- Original Message -----
>>> From: "Steve Lee" <[hidden email]>
>>> To: "Bryan Garaventa" <[hidden email]>
>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>> Sent: Monday, July 21, 2008 11:09 PM
>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>
>>>
>>>> Sorry If I didn't make it clear but you should run a batch file called
>>>> something like vcvars.bat in you command prompt first. This will set
>>>> up the environment variable so the compilers find the correct files.
>>>> This sounds like the proble. You should nto have to copy files and
>>>> that can cause confusion due to the way the compiler searches for
>>>> included files. The exact file name various with the version of the
>>>> tools you use. The only complication comes as you often have set
>>>> things up for both the VC and SDK.
>>>>
>>>> If you use the Mozilla Build system it should sort this out for you
>>>> and gives you a nice UNIX like shell.
>>>>
>>>> Steve
>>>>
>>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>>> Actually, this output doesn't look like C++ header code, but rather an
>>>>> error
>>>>> log from the midl compiler.
>>>>>
>>>>> I've attached the generated files from midl.exe from the cmd prompt in
>>>>> case
>>>>> anyone would like to take a look, and hopefully, can provide a totally
>>>>> brilliant insight that can restore my faith in Microsoft products as a
>>>>> whole
>>>>> in one fell swoop?
>>>>>
>>>>> I can't say I understand it. This time I used the 2008 Vista SDK to
>>>>> make
>>>>> sure I have the most recent files.
>>>>>
>>>>> Also, I used the /I switch to designate the include folder, for
>>>>> instance
>>>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>>>> ISimpleDOMNode.idl
>>>>> So that none of the includes could be accidentally omitted.
>>>>>
>>>>> I didn't get any errors in the command prompt, but in the .h file, it
>>>>> says
>>>>> that I need a more recent version of rcndr.h and that I missing
>>>>> windows.h,
>>>>> which is confusing. This is a 2008 update package so it should contain
>>>>> the
>>>>> latest header files, I would assume anyway. Also, I checked the
>>>>> include
>>>>> directory and it does contain a windows.h file in the same folder as
>>>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>>>
>>>>> I wonder if MS has ever heard of the KISS principle...
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------
>>>>> Bryan Garaventa
>>>>> Senior Accessibility Engineer
>>>>> SSB + BART Group
>>>>> [hidden email]
>>>>> www.SSBBartGroup.com
>>>>> Accessibility-On-Demand
>>>>>
>>>>> ----- Original Message ----- From: "Bryan Garaventa"
>>>>> <[hidden email]>
>>>>> To: "dev-accessibility Firefox" <[hidden email]>
>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>> Sent: Monday, July 21, 2008 1:24 PM
>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>
>>>>>
>>>>>> Thanks, that's no problem.
>>>>>>
>>>>>> I'm using cmd to access midl.exe, using the docs at
>>>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>>>> reference.
>>>>>>
>>>>>> Many of the included files appear to be spread around various
>>>>>> directories
>>>>>> though, so it took me a while to track the errors enough to gather
>>>>>> all
>>>>>> of
>>>>>> these files into one main directory. This includes cl.exe and the
>>>>>> other
>>>>>> referenced dll. So far, I've been using those files found in the
>>>>>> Program
>>>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found
>>>>>> two
>>>>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>>>>> Phone
>>>>>> folder, but I couldn't find any references to determine if these
>>>>>> files
>>>>>> are
>>>>>> device dependant. I'm not having much luck finding any docs that
>>>>>> really
>>>>>> explain how Midl is supposed to be used, and which files are directly
>>>>>> relevant for a standard Win32 environment.
>>>>>>
>>>>>> I did try the compilation without the /nocpp switch, and also leaving
>>>>>> out
>>>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>>>> default
>>>>>> switches should automatically generate the C headers and the TLB
>>>>>> within
>>>>>> the
>>>>>> same directory. Well, the C headers appear to generate fine, no
>>>>>> errors
>>>>>> appear within the command prompt during the compilation. This is
>>>>>> using
>>>>>> the
>>>>>> same objidl.idl file as mentioned before, located in the Program
>>>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder.
>>>>>> However,
>>>>>> no
>>>>>> TLB file is generated. Only when I disable the C processor using
>>>>>> /no_cpp
>>>>>> or
>>>>>> /nocpp, does this syntax error occur.
>>>>>>
>>>>>> I'm hoping that I'm missing something simple, like not changing the
>>>>>> correct
>>>>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>>>>> since
>>>>>> I
>>>>>> wouldn't believe I was actually going nuts.
>>>>>>
>>>>>> Just in case, these are the lines I changed within the
>>>>>> ISimpleDOMNode.idl
>>>>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>>>>> constants from negative to positive values.)
>>>>>>
>>>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>>>
>>>>>> Could this be the problem?
>>>>>>
>>>>>> I appreciate the help, but it's no rush.
>>>>>>
>>>>>> Best wishes,
>>>>>>
>>>>>> Bryan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>> Bryan Garaventa
>>>>>> Senior Accessibility Engineer
>>>>>> SSB + BART Group
>>>>>> [hidden email]
>>>>>> www.SSBBartGroup.com
>>>>>> Accessibility-On-Demand
>>>>>>
>>>>>>
>>>>>> ----- Original Message ----- From: "Steve Lee"
>>>>>> <[hidden email]>
>>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>
>>>>>>
>>>>>>> Reposting to list
>>>>>>>
>>>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>>>>>> build going and have run out of time to look more till next week :-(
>>>>>>>
>>>>>>> One thing are you sure /nocpp is correct? Something may want the C
>>>>>>> pre
>>>>>>> processor, which might be why it's barfing in the comments. Thats a
>>>>>>> pretty basic syntax error indicating it really confused with the
>>>>>>> source. I'm also not sure you need /tlb either.
>>>>>>>
>>>>>>> You should check that INCLUDE is set correctly, it might not be
>>>>>>> using
>>>>>>> the right files or your local copies.
>>>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>>>> start-msvcN.bat it should be all set up for you (though I just had
>>>>>>> to
>>>>>>> patch it for VC9Express)
>>>>>>>
>>>>>>> Steve
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev-accessibility mailing list
>>>>>> [hidden email]
>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>
>>>>> _______________________________________________
>>>>> dev-accessibility mailing list
>>>>> [hidden email]
>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Steve Lee
>>>> Open Source Assistive Technology Software and Accessibility
>>>> fullmeasure.co.uk
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>> _______________________________________________
>>> dev-accessibility mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>
>>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>
>
>
> --
> Steve Lee
> Open Source Assistive Technology Software and Accessibility
> fullmeasure.co.uk

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Fwd: Not managing to build .tlb for SimpleDOMNode.idl

Steve Lee-3
---------- Forwarded message ----------
From: Steve Lee <[hidden email]>
Date: 2008/7/23
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
To: Bryan Garaventa <[hidden email]>


I will have a quick go tomorrow. I understand the frustration,
building with C tools can be like that if you don't have exatly the
right setup.

Can you remind me why to want the tlb? if it is for something like VB
access to Firefox then AFAIK it's only half the story and there is no
IDispatch implementation to actually respond to any requests you make.
Compiled languages usually use the IDL source directly during
compilation and so don't need a TLB at runtime.

Building Mozilla is pretty simple: grab Visual Studio 9 Express, the
Windows Vista SDK and the server 2003 R2 Platform SDK and then install
and run the mozilla build system, grab the source and build. Follow
the Windows specific instructions from
http://developer.mozilla.org/en/docs/Build_Documentation which is very
good docs now.

Steve

2008/7/23 Bryan Garaventa <[hidden email]>:

> That's alright, I understand. What I'm trying to do is amazingly simple, and
> that's where all of my frustration comes into it.
>
> I just need the compiled ISimpleDOMNode.tlb class lib file. It doesn't
> matter where it comes from, all that is needed is if the environment switch
> is set for Win32, this would do the trick.
>
> I'm building an ActiveX control, and need to use the ISimpleDOMNode.tlb as a
> reference in order for it to work properly.
>
> If anyone can successfully compile the ISimpleDOMNode.tlb and just send it
> to me as an attachment, that would solve everything. I have no idea why it
> isn't working for me, but it sounds like everyone except me can accomplish
> it successfully. I've written about the Midl compiler issue in the MSDN
> forums, but haven't received any reply as yet.
>
> This missing class lib file is my proverbial wrench in the gears, the lack
> of it is stopping any progress.
>
> The reason why I haven't compiled Mozilla is that I'm not really sure how.
> It doesn't sound like this would solve the problem though, since I would
> still need the ISimpleDOMNode.tlb class lib file. Is this class lib
> automatically created when Mozilla is compiled? Can I find this in my
> current installation of Mozilla?
>
> It's all a bit discouraging... How something so small can be such a large
> problem.
>
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> [hidden email]
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
> ----- Original Message -----
> From: "Steve Lee" <[hidden email]>
> To: "Bryan Garaventa" <[hidden email]>
> Cc: "dev-accessibility Firefox" <[hidden email]>
> Sent: Wednesday, July 23, 2008 1:54 AM
> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>
>
>> Bryan, I'm just stepping back from this and thinking that if you are
>> really trying to add to a files that already exists in the Mozilla
>> source tree the best solution is to use mozilla build to build the
>> original and then chat to the guys working on that area on IRC in
>> #a11y if you still have problems.
>>
>> Perhaps that will give you a less frustrating time as I know how
>> depressing it can be getting a build env up with MS tools as there are
>> many configs and options and interactions. Timing may be a small issue
>> as I think the devs are in China.
>>
>> Just an idea
>>
>> Cheers
>>
>> Steve
>>
>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>> I guess attachments don't work for the list. As an alt I've uploaded the
>>> zip
>>> to
>>> http://gutterstar.net/ISimpleDOMNode.zip
>>>
>>> This contains the files
>>> ISimpleDOMNode.idl
>>> dlldata.c
>>> ISimpleDOMNode.h
>>> ISimpleDOMNode_i.c
>>> ISimpleDOMNode_p.c
>>>
>>> Other than ISimpleDOMNode.idl, these other files are all that the midl
>>> compiler will generate.
>>>
>>>
>>> --------------------------------------------------------------------------------
>>> Bryan Garaventa
>>> Senior Accessibility Engineer
>>> SSB + BART Group
>>> [hidden email]
>>> www.SSBBartGroup.com
>>> Accessibility-On-Demand
>>>
>>> ----- Original Message -----
>>> From: "Bryan Garaventa" <[hidden email]>
>>> To: "dev-accessibility Firefox" <[hidden email]>
>>> Sent: Tuesday, July 22, 2008 10:59 AM
>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>
>>>
>>>> Thanks, sadly it gives me the same behavior.
>>>>
>>>> These were my steps...
>>>> 1) I went to
>>>> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
>>>> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
>>>> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not really
>>>> sure
>>>> if any of this made a difference or not really.)
>>>> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual Studio
>>>> Tools , I opened Visual Studio 2008 Command Prompt.
>>>> 5) Ran vcvarsall.bat to set up the rest of the variables.
>>>> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
>>>> midl ISimpleDOMNode.idl
>>>>
>>>> I've attached the only generated files. This includes the
>>>> ISimpleDOMNode.idl
>>>> file for reference. No TLB, just .c files.
>>>>
>>>> Would it be possible for me to just create a C++ project in VS.net using
>>>> these C files to make my own class lib? This shouldn't be necessary, but
>>>> I
>>>> don't know what else to try.
>>>>
>>>> Arg,
>>>>
>>>> Bryan
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Bryan Garaventa
>>>> Senior Accessibility Engineer
>>>> SSB + BART Group
>>>> [hidden email]
>>>> www.SSBBartGroup.com
>>>> Accessibility-On-Demand
>>>>
>>>> ----- Original Message -----
>>>> From: "Steve Lee" <[hidden email]>
>>>> To: "Bryan Garaventa" <[hidden email]>
>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>> Sent: Monday, July 21, 2008 11:09 PM
>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>
>>>>
>>>>> Sorry If I didn't make it clear but you should run a batch file called
>>>>> something like vcvars.bat in you command prompt first. This will set
>>>>> up the environment variable so the compilers find the correct files.
>>>>> This sounds like the proble. You should nto have to copy files and
>>>>> that can cause confusion due to the way the compiler searches for
>>>>> included files. The exact file name various with the version of the
>>>>> tools you use. The only complication comes as you often have set
>>>>> things up for both the VC and SDK.
>>>>>
>>>>> If you use the Mozilla Build system it should sort this out for you
>>>>> and gives you a nice UNIX like shell.
>>>>>
>>>>> Steve
>>>>>
>>>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>>>> Actually, this output doesn't look like C++ header code, but rather an
>>>>>> error
>>>>>> log from the midl compiler.
>>>>>>
>>>>>> I've attached the generated files from midl.exe from the cmd prompt in
>>>>>> case
>>>>>> anyone would like to take a look, and hopefully, can provide a totally
>>>>>> brilliant insight that can restore my faith in Microsoft products as a
>>>>>> whole
>>>>>> in one fell swoop?
>>>>>>
>>>>>> I can't say I understand it. This time I used the 2008 Vista SDK to
>>>>>> make
>>>>>> sure I have the most recent files.
>>>>>>
>>>>>> Also, I used the /I switch to designate the include folder, for
>>>>>> instance
>>>>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>>>>> ISimpleDOMNode.idl
>>>>>> So that none of the includes could be accidentally omitted.
>>>>>>
>>>>>> I didn't get any errors in the command prompt, but in the .h file, it
>>>>>> says
>>>>>> that I need a more recent version of rcndr.h and that I missing
>>>>>> windows.h,
>>>>>> which is confusing. This is a 2008 update package so it should contain
>>>>>> the
>>>>>> latest header files, I would assume anyway. Also, I checked the
>>>>>> include
>>>>>> directory and it does contain a windows.h file in the same folder as
>>>>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>>>>
>>>>>> I wonder if MS has ever heard of the KISS principle...
>>>>>>
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>> Bryan Garaventa
>>>>>> Senior Accessibility Engineer
>>>>>> SSB + BART Group
>>>>>> [hidden email]
>>>>>> www.SSBBartGroup.com
>>>>>> Accessibility-On-Demand
>>>>>>
>>>>>> ----- Original Message ----- From: "Bryan Garaventa"
>>>>>> <[hidden email]>
>>>>>> To: "dev-accessibility Firefox" <[hidden email]>
>>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>>> Sent: Monday, July 21, 2008 1:24 PM
>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>
>>>>>>
>>>>>>> Thanks, that's no problem.
>>>>>>>
>>>>>>> I'm using cmd to access midl.exe, using the docs at
>>>>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>>>>> reference.
>>>>>>>
>>>>>>> Many of the included files appear to be spread around various
>>>>>>> directories
>>>>>>> though, so it took me a while to track the errors enough to gather
>>>>>>> all
>>>>>>> of
>>>>>>> these files into one main directory. This includes cl.exe and the
>>>>>>> other
>>>>>>> referenced dll. So far, I've been using those files found in the
>>>>>>> Program
>>>>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I found
>>>>>>> two
>>>>>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>>>>>> Phone
>>>>>>> folder, but I couldn't find any references to determine if these
>>>>>>> files
>>>>>>> are
>>>>>>> device dependant. I'm not having much luck finding any docs that
>>>>>>> really
>>>>>>> explain how Midl is supposed to be used, and which files are directly
>>>>>>> relevant for a standard Win32 environment.
>>>>>>>
>>>>>>> I did try the compilation without the /nocpp switch, and also leaving
>>>>>>> out
>>>>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>>>>> default
>>>>>>> switches should automatically generate the C headers and the TLB
>>>>>>> within
>>>>>>> the
>>>>>>> same directory. Well, the C headers appear to generate fine, no
>>>>>>> errors
>>>>>>> appear within the command prompt during the compilation. This is
>>>>>>> using
>>>>>>> the
>>>>>>> same objidl.idl file as mentioned before, located in the Program
>>>>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder.
>>>>>>> However,
>>>>>>> no
>>>>>>> TLB file is generated. Only when I disable the C processor using
>>>>>>> /no_cpp
>>>>>>> or
>>>>>>> /nocpp, does this syntax error occur.
>>>>>>>
>>>>>>> I'm hoping that I'm missing something simple, like not changing the
>>>>>>> correct
>>>>>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>>>>>> since
>>>>>>> I
>>>>>>> wouldn't believe I was actually going nuts.
>>>>>>>
>>>>>>> Just in case, these are the lines I changed within the
>>>>>>> ISimpleDOMNode.idl
>>>>>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>>>>>> constants from negative to positive values.)
>>>>>>>
>>>>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>>>>
>>>>>>> Could this be the problem?
>>>>>>>
>>>>>>> I appreciate the help, but it's no rush.
>>>>>>>
>>>>>>> Best wishes,
>>>>>>>
>>>>>>> Bryan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --------------------------------------------------------------------------------
>>>>>>> Bryan Garaventa
>>>>>>> Senior Accessibility Engineer
>>>>>>> SSB + BART Group
>>>>>>> [hidden email]
>>>>>>> www.SSBBartGroup.com
>>>>>>> Accessibility-On-Demand
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message ----- From: "Steve Lee"
>>>>>>> <[hidden email]>
>>>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>
>>>>>>>
>>>>>>>> Reposting to list
>>>>>>>>
>>>>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a mozilla
>>>>>>>> build going and have run out of time to look more till next week :-(
>>>>>>>>
>>>>>>>> One thing are you sure /nocpp is correct? Something may want the C
>>>>>>>> pre
>>>>>>>> processor, which might be why it's barfing in the comments. Thats a
>>>>>>>> pretty basic syntax error indicating it really confused with the
>>>>>>>> source. I'm also not sure you need /tlb either.
>>>>>>>>
>>>>>>>> You should check that INCLUDE is set correctly, it might not be
>>>>>>>> using
>>>>>>>> the right files or your local copies.
>>>>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>>>>> start-msvcN.bat it should be all set up for you (though I just had
>>>>>>>> to
>>>>>>>> patch it for VC9Express)
>>>>>>>>
>>>>>>>> Steve
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev-accessibility mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev-accessibility mailing list
>>>>>> [hidden email]
>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Steve Lee
>>>>> Open Source Assistive Technology Software and Accessibility
>>>>> fullmeasure.co.uk
>>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>> _______________________________________________
>>>> dev-accessibility mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>
>>>
>>> _______________________________________________
>>> dev-accessibility mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>
>>
>>
>>
>> --
>> Steve Lee
>> Open Source Assistive Technology Software and Accessibility
>> fullmeasure.co.uk
>
> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility
>



--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk



--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk
_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
In reply to this post by Bryan Garaventa-2
Thanks, what I was hoping to do is use a function within the activeX to call
AccessibleObjectFromEvent, and grab the IAccessible object from the Firefox
content window handle.

Is it necessary for Firefox to have IDispatch support for me to use
AccessibleObjectFromEvent?



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Sent: Wednesday, July 23, 2008 12:12 PM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


>I will have a quick go tomorrow. I understand the frustration,
> building with C tools can be like that if you don't have exatly the
> right setup.
>
> Can you remind me why to want the tlb? if it is for something like VB
> access to Firefox then AFAIK it's only half the story and there is no
> IDispatch implementation to actually respond to any requests you make.
> Compiled languages usually use the IDL source directly during
> compilation and so don't need a TLB at runtime.
>
> Building Mozilla is pretty simple: grab Visual Studio 9 Express, the
> Windows Vista SDK and the server 2003 R2 Platform SDK and then install
> and run the mozilla build system, grab the source and build. Follow
> the Windows specific instructions from
> http://developer.mozilla.org/en/docs/Build_Documentation which is very
> good docs now.
>
> Steve
>
> 2008/7/23 Bryan Garaventa <[hidden email]>:
>> That's alright, I understand. What I'm trying to do is amazingly simple,
>> and
>> that's where all of my frustration comes into it.
>>
>> I just need the compiled ISimpleDOMNode.tlb class lib file. It doesn't
>> matter where it comes from, all that is needed is if the environment
>> switch
>> is set for Win32, this would do the trick.
>>
>> I'm building an ActiveX control, and need to use the ISimpleDOMNode.tlb
>> as a
>> reference in order for it to work properly.
>>
>> If anyone can successfully compile the ISimpleDOMNode.tlb and just send
>> it
>> to me as an attachment, that would solve everything. I have no idea why
>> it
>> isn't working for me, but it sounds like everyone except me can
>> accomplish
>> it successfully. I've written about the Midl compiler issue in the MSDN
>> forums, but haven't received any reply as yet.
>>
>> This missing class lib file is my proverbial wrench in the gears, the
>> lack
>> of it is stopping any progress.
>>
>> The reason why I haven't compiled Mozilla is that I'm not really sure
>> how.
>> It doesn't sound like this would solve the problem though, since I would
>> still need the ISimpleDOMNode.tlb class lib file. Is this class lib
>> automatically created when Mozilla is compiled? Can I find this in my
>> current installation of Mozilla?
>>
>> It's all a bit discouraging... How something so small can be such a large
>> problem.
>>
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>> ----- Original Message -----
>> From: "Steve Lee" <[hidden email]>
>> To: "Bryan Garaventa" <[hidden email]>
>> Cc: "dev-accessibility Firefox" <[hidden email]>
>> Sent: Wednesday, July 23, 2008 1:54 AM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>> Bryan, I'm just stepping back from this and thinking that if you are
>>> really trying to add to a files that already exists in the Mozilla
>>> source tree the best solution is to use mozilla build to build the
>>> original and then chat to the guys working on that area on IRC in
>>> #a11y if you still have problems.
>>>
>>> Perhaps that will give you a less frustrating time as I know how
>>> depressing it can be getting a build env up with MS tools as there are
>>> many configs and options and interactions. Timing may be a small issue
>>> as I think the devs are in China.
>>>
>>> Just an idea
>>>
>>> Cheers
>>>
>>> Steve
>>>
>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>> I guess attachments don't work for the list. As an alt I've uploaded
>>>> the
>>>> zip
>>>> to
>>>> http://gutterstar.net/ISimpleDOMNode.zip
>>>>
>>>> This contains the files
>>>> ISimpleDOMNode.idl
>>>> dlldata.c
>>>> ISimpleDOMNode.h
>>>> ISimpleDOMNode_i.c
>>>> ISimpleDOMNode_p.c
>>>>
>>>> Other than ISimpleDOMNode.idl, these other files are all that the midl
>>>> compiler will generate.
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Bryan Garaventa
>>>> Senior Accessibility Engineer
>>>> SSB + BART Group
>>>> [hidden email]
>>>> www.SSBBartGroup.com
>>>> Accessibility-On-Demand
>>>>
>>>> ----- Original Message -----
>>>> From: "Bryan Garaventa" <[hidden email]>
>>>> To: "dev-accessibility Firefox" <[hidden email]>
>>>> Sent: Tuesday, July 22, 2008 10:59 AM
>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>
>>>>
>>>>> Thanks, sadly it gives me the same behavior.
>>>>>
>>>>> These were my steps...
>>>>> 1) I went to
>>>>> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
>>>>> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
>>>>> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not
>>>>> really
>>>>> sure
>>>>> if any of this made a difference or not really.)
>>>>> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual
>>>>> Studio
>>>>> Tools , I opened Visual Studio 2008 Command Prompt.
>>>>> 5) Ran vcvarsall.bat to set up the rest of the variables.
>>>>> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I entered
>>>>> midl ISimpleDOMNode.idl
>>>>>
>>>>> I've attached the only generated files. This includes the
>>>>> ISimpleDOMNode.idl
>>>>> file for reference. No TLB, just .c files.
>>>>>
>>>>> Would it be possible for me to just create a C++ project in VS.net
>>>>> using
>>>>> these C files to make my own class lib? This shouldn't be necessary,
>>>>> but
>>>>> I
>>>>> don't know what else to try.
>>>>>
>>>>> Arg,
>>>>>
>>>>> Bryan
>>>>>
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------
>>>>> Bryan Garaventa
>>>>> Senior Accessibility Engineer
>>>>> SSB + BART Group
>>>>> [hidden email]
>>>>> www.SSBBartGroup.com
>>>>> Accessibility-On-Demand
>>>>>
>>>>> ----- Original Message -----
>>>>> From: "Steve Lee" <[hidden email]>
>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>>> Sent: Monday, July 21, 2008 11:09 PM
>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>
>>>>>
>>>>>> Sorry If I didn't make it clear but you should run a batch file
>>>>>> called
>>>>>> something like vcvars.bat in you command prompt first. This will set
>>>>>> up the environment variable so the compilers find the correct files.
>>>>>> This sounds like the proble. You should nto have to copy files and
>>>>>> that can cause confusion due to the way the compiler searches for
>>>>>> included files. The exact file name various with the version of the
>>>>>> tools you use. The only complication comes as you often have set
>>>>>> things up for both the VC and SDK.
>>>>>>
>>>>>> If you use the Mozilla Build system it should sort this out for you
>>>>>> and gives you a nice UNIX like shell.
>>>>>>
>>>>>> Steve
>>>>>>
>>>>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>>>>> Actually, this output doesn't look like C++ header code, but rather
>>>>>>> an
>>>>>>> error
>>>>>>> log from the midl compiler.
>>>>>>>
>>>>>>> I've attached the generated files from midl.exe from the cmd prompt
>>>>>>> in
>>>>>>> case
>>>>>>> anyone would like to take a look, and hopefully, can provide a
>>>>>>> totally
>>>>>>> brilliant insight that can restore my faith in Microsoft products as
>>>>>>> a
>>>>>>> whole
>>>>>>> in one fell swoop?
>>>>>>>
>>>>>>> I can't say I understand it. This time I used the 2008 Vista SDK to
>>>>>>> make
>>>>>>> sure I have the most recent files.
>>>>>>>
>>>>>>> Also, I used the /I switch to designate the include folder, for
>>>>>>> instance
>>>>>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>>>>>> ISimpleDOMNode.idl
>>>>>>> So that none of the includes could be accidentally omitted.
>>>>>>>
>>>>>>> I didn't get any errors in the command prompt, but in the .h file,
>>>>>>> it
>>>>>>> says
>>>>>>> that I need a more recent version of rcndr.h and that I missing
>>>>>>> windows.h,
>>>>>>> which is confusing. This is a 2008 update package so it should
>>>>>>> contain
>>>>>>> the
>>>>>>> latest header files, I would assume anyway. Also, I checked the
>>>>>>> include
>>>>>>> directory and it does contain a windows.h file in the same folder as
>>>>>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>>>>>
>>>>>>> I wonder if MS has ever heard of the KISS principle...
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --------------------------------------------------------------------------------
>>>>>>> Bryan Garaventa
>>>>>>> Senior Accessibility Engineer
>>>>>>> SSB + BART Group
>>>>>>> [hidden email]
>>>>>>> www.SSBBartGroup.com
>>>>>>> Accessibility-On-Demand
>>>>>>>
>>>>>>> ----- Original Message ----- From: "Bryan Garaventa"
>>>>>>> <[hidden email]>
>>>>>>> To: "dev-accessibility Firefox"
>>>>>>> <[hidden email]>
>>>>>>> Cc: "dev-accessibility Firefox"
>>>>>>> <[hidden email]>
>>>>>>> Sent: Monday, July 21, 2008 1:24 PM
>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>
>>>>>>>
>>>>>>>> Thanks, that's no problem.
>>>>>>>>
>>>>>>>> I'm using cmd to access midl.exe, using the docs at
>>>>>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>>>>>> reference.
>>>>>>>>
>>>>>>>> Many of the included files appear to be spread around various
>>>>>>>> directories
>>>>>>>> though, so it took me a while to track the errors enough to gather
>>>>>>>> all
>>>>>>>> of
>>>>>>>> these files into one main directory. This includes cl.exe and the
>>>>>>>> other
>>>>>>>> referenced dll. So far, I've been using those files found in the
>>>>>>>> Program
>>>>>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I
>>>>>>>> found
>>>>>>>> two
>>>>>>>> objidl.idl files, one in the Smart Devices folder, and in the Smart
>>>>>>>> Phone
>>>>>>>> folder, but I couldn't find any references to determine if these
>>>>>>>> files
>>>>>>>> are
>>>>>>>> device dependant. I'm not having much luck finding any docs that
>>>>>>>> really
>>>>>>>> explain how Midl is supposed to be used, and which files are
>>>>>>>> directly
>>>>>>>> relevant for a standard Win32 environment.
>>>>>>>>
>>>>>>>> I did try the compilation without the /nocpp switch, and also
>>>>>>>> leaving
>>>>>>>> out
>>>>>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>>>>>> default
>>>>>>>> switches should automatically generate the C headers and the TLB
>>>>>>>> within
>>>>>>>> the
>>>>>>>> same directory. Well, the C headers appear to generate fine, no
>>>>>>>> errors
>>>>>>>> appear within the command prompt during the compilation. This is
>>>>>>>> using
>>>>>>>> the
>>>>>>>> same objidl.idl file as mentioned before, located in the Program
>>>>>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder.
>>>>>>>> However,
>>>>>>>> no
>>>>>>>> TLB file is generated. Only when I disable the C processor using
>>>>>>>> /no_cpp
>>>>>>>> or
>>>>>>>> /nocpp, does this syntax error occur.
>>>>>>>>
>>>>>>>> I'm hoping that I'm missing something simple, like not changing the
>>>>>>>> correct
>>>>>>>> info in the ISimpleDOMNode.idl file, which would be a happy mistake
>>>>>>>> since
>>>>>>>> I
>>>>>>>> wouldn't believe I was actually going nuts.
>>>>>>>>
>>>>>>>> Just in case, these are the lines I changed within the
>>>>>>>> ISimpleDOMNode.idl
>>>>>>>> file based on Aaron's discovery earlier. (Changing all of the iDISP
>>>>>>>> constants from negative to positive values.)
>>>>>>>>
>>>>>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>>>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>>>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>>>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>>>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>>>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>>>>>
>>>>>>>> Could this be the problem?
>>>>>>>>
>>>>>>>> I appreciate the help, but it's no rush.
>>>>>>>>
>>>>>>>> Best wishes,
>>>>>>>>
>>>>>>>> Bryan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>> Bryan Garaventa
>>>>>>>> Senior Accessibility Engineer
>>>>>>>> SSB + BART Group
>>>>>>>> [hidden email]
>>>>>>>> www.SSBBartGroup.com
>>>>>>>> Accessibility-On-Demand
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original Message ----- From: "Steve Lee"
>>>>>>>> <[hidden email]>
>>>>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>>>>> Cc: "dev-accessibility Firefox"
>>>>>>>> <[hidden email]>
>>>>>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>>
>>>>>>>>
>>>>>>>>> Reposting to list
>>>>>>>>>
>>>>>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a
>>>>>>>>> mozilla
>>>>>>>>> build going and have run out of time to look more till next week
>>>>>>>>> :-(
>>>>>>>>>
>>>>>>>>> One thing are you sure /nocpp is correct? Something may want the C
>>>>>>>>> pre
>>>>>>>>> processor, which might be why it's barfing in the comments. Thats
>>>>>>>>> a
>>>>>>>>> pretty basic syntax error indicating it really confused with the
>>>>>>>>> source. I'm also not sure you need /tlb either.
>>>>>>>>>
>>>>>>>>> You should check that INCLUDE is set correctly, it might not be
>>>>>>>>> using
>>>>>>>>> the right files or your local copies.
>>>>>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>>>>>> start-msvcN.bat it should be all set up for you (though I just had
>>>>>>>>> to
>>>>>>>>> patch it for VC9Express)
>>>>>>>>>
>>>>>>>>> Steve
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> dev-accessibility mailing list
>>>>>>>> [hidden email]
>>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev-accessibility mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Steve Lee
>>>>>> Open Source Assistive Technology Software and Accessibility
>>>>>> fullmeasure.co.uk
>>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>>
>>>>
>>>>> _______________________________________________
>>>>> dev-accessibility mailing list
>>>>> [hidden email]
>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>
>>>>
>>>> _______________________________________________
>>>> dev-accessibility mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>
>>>
>>>
>>>
>>> --
>>> Steve Lee
>>> Open Source Assistive Technology Software and Accessibility
>>> fullmeasure.co.uk
>>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>
>
>
> --
> Steve Lee
> Open Source Assistive Technology Software and Accessibility
> fullmeasure.co.uk

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
Basically it's a COM Service, in the form of an ActiveX compiled in VB.

I've imported Oleacc, so the ActiveX has access to the
AccessibleObjectFromEvent function at runtime.

In this way, I can call the AccessibleObjectFromEvent function from another
app when using this ActiveX by passing the necessary window handle, and then
parse the returned IAccessible object within the ActiveX itself.

This should work, since AccessibleObjectFromEvent is part of MSAA.

I don't see why, if I can get the IAccessible object in this manner, that I
could not use the ISimpleDOMNode.tlb type lib within the COM Service to
convert the IAccessible object into a DOM object using QueryService. After
all, the IAccessible object will already be stored in a local variable at
this point within the ActiveX control.

The only snag that I can see regarding this process, is if the
AccessibleObjectFromEvent function cannot communicate with an app that does
not support IDispatch. This is why I was asking if Firefox could not expose
an IAccessible object if another application used AccessibleObjectFromEvent
to retrieve this using the window handle of the content window.

Since the IAccessible object is supposed to be exposed for accessibility
within Firefox though, this wouldn't make much sense if IDispatch within
Firefox is necessary to use AccessibleObjectFromEvent.

That would be like saying that you can use AccessibleObjectFromEvent to get
the IAccessible object within Firefox, but you can't use
AccessibleObjectFromEvent to get the IAccessible object within Firefox.

Going on the premise that it is possible to get the IAccessible object
though, this is why I would need the ISimpleDOMNode tlb.

Hope this helps,

Bryan



--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Sent: Wednesday, July 23, 2008 12:50 PM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> What exactly do you mean 'within the ActiveX'?
>
> Steve
>
> 2008/7/23 Bryan Garaventa <[hidden email]>:
>> Thanks, what I was hoping to do is use a function within the activeX to
>> call
>> AccessibleObjectFromEvent, and grab the IAccessible object from the
>> Firefox
>> content window handle.
>>
>> Is it necessary for Firefox to have IDispatch support for me to use
>> AccessibleObjectFromEvent?
>>
>>
>>
>> --------------------------------------------------------------------------------
>> Bryan Garaventa
>> Senior Accessibility Engineer
>> SSB + BART Group
>> [hidden email]
>> www.SSBBartGroup.com
>> Accessibility-On-Demand
>>
>> ----- Original Message -----
>> From: "Steve Lee" <[hidden email]>
>> To: "Bryan Garaventa" <[hidden email]>
>> Sent: Wednesday, July 23, 2008 12:12 PM
>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>
>>
>>>I will have a quick go tomorrow. I understand the frustration,
>>> building with C tools can be like that if you don't have exatly the
>>> right setup.
>>>
>>> Can you remind me why to want the tlb? if it is for something like VB
>>> access to Firefox then AFAIK it's only half the story and there is no
>>> IDispatch implementation to actually respond to any requests you make.
>>> Compiled languages usually use the IDL source directly during
>>> compilation and so don't need a TLB at runtime.
>>>
>>> Building Mozilla is pretty simple: grab Visual Studio 9 Express, the
>>> Windows Vista SDK and the server 2003 R2 Platform SDK and then install
>>> and run the mozilla build system, grab the source and build. Follow
>>> the Windows specific instructions from
>>> http://developer.mozilla.org/en/docs/Build_Documentation which is very
>>> good docs now.
>>>
>>> Steve
>>>
>>> 2008/7/23 Bryan Garaventa <[hidden email]>:
>>>> That's alright, I understand. What I'm trying to do is amazingly
>>>> simple,
>>>> and
>>>> that's where all of my frustration comes into it.
>>>>
>>>> I just need the compiled ISimpleDOMNode.tlb class lib file. It doesn't
>>>> matter where it comes from, all that is needed is if the environment
>>>> switch
>>>> is set for Win32, this would do the trick.
>>>>
>>>> I'm building an ActiveX control, and need to use the ISimpleDOMNode.tlb
>>>> as a
>>>> reference in order for it to work properly.
>>>>
>>>> If anyone can successfully compile the ISimpleDOMNode.tlb and just send
>>>> it
>>>> to me as an attachment, that would solve everything. I have no idea why
>>>> it
>>>> isn't working for me, but it sounds like everyone except me can
>>>> accomplish
>>>> it successfully. I've written about the Midl compiler issue in the MSDN
>>>> forums, but haven't received any reply as yet.
>>>>
>>>> This missing class lib file is my proverbial wrench in the gears, the
>>>> lack
>>>> of it is stopping any progress.
>>>>
>>>> The reason why I haven't compiled Mozilla is that I'm not really sure
>>>> how.
>>>> It doesn't sound like this would solve the problem though, since I
>>>> would
>>>> still need the ISimpleDOMNode.tlb class lib file. Is this class lib
>>>> automatically created when Mozilla is compiled? Can I find this in my
>>>> current installation of Mozilla?
>>>>
>>>> It's all a bit discouraging... How something so small can be such a
>>>> large
>>>> problem.
>>>>
>>>>
>>>>
>>>> --------------------------------------------------------------------------------
>>>> Bryan Garaventa
>>>> Senior Accessibility Engineer
>>>> SSB + BART Group
>>>> [hidden email]
>>>> www.SSBBartGroup.com
>>>> Accessibility-On-Demand
>>>>
>>>> ----- Original Message -----
>>>> From: "Steve Lee" <[hidden email]>
>>>> To: "Bryan Garaventa" <[hidden email]>
>>>> Cc: "dev-accessibility Firefox" <[hidden email]>
>>>> Sent: Wednesday, July 23, 2008 1:54 AM
>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>
>>>>
>>>>> Bryan, I'm just stepping back from this and thinking that if you are
>>>>> really trying to add to a files that already exists in the Mozilla
>>>>> source tree the best solution is to use mozilla build to build the
>>>>> original and then chat to the guys working on that area on IRC in
>>>>> #a11y if you still have problems.
>>>>>
>>>>> Perhaps that will give you a less frustrating time as I know how
>>>>> depressing it can be getting a build env up with MS tools as there are
>>>>> many configs and options and interactions. Timing may be a small issue
>>>>> as I think the devs are in China.
>>>>>
>>>>> Just an idea
>>>>>
>>>>> Cheers
>>>>>
>>>>> Steve
>>>>>
>>>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>>>> I guess attachments don't work for the list. As an alt I've uploaded
>>>>>> the
>>>>>> zip
>>>>>> to
>>>>>> http://gutterstar.net/ISimpleDOMNode.zip
>>>>>>
>>>>>> This contains the files
>>>>>> ISimpleDOMNode.idl
>>>>>> dlldata.c
>>>>>> ISimpleDOMNode.h
>>>>>> ISimpleDOMNode_i.c
>>>>>> ISimpleDOMNode_p.c
>>>>>>
>>>>>> Other than ISimpleDOMNode.idl, these other files are all that the
>>>>>> midl
>>>>>> compiler will generate.
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>> Bryan Garaventa
>>>>>> Senior Accessibility Engineer
>>>>>> SSB + BART Group
>>>>>> [hidden email]
>>>>>> www.SSBBartGroup.com
>>>>>> Accessibility-On-Demand
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Bryan Garaventa" <[hidden email]>
>>>>>> To: "dev-accessibility Firefox" <[hidden email]>
>>>>>> Sent: Tuesday, July 22, 2008 10:59 AM
>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>
>>>>>>
>>>>>>> Thanks, sadly it gives me the same behavior.
>>>>>>>
>>>>>>> These were my steps...
>>>>>>> 1) I went to
>>>>>>> C:\Program Files\Microsoft SDKs\Windows\v6.0\Setup
>>>>>>> 2) Ran VCIntegrate.exe to synchronize the most recent folder paths.
>>>>>>> 3) Ran VCDetect.Exe and VCInit.bat to set the app dirs. (I'm not
>>>>>>> really
>>>>>>> sure
>>>>>>> if any of this made a difference or not really.)
>>>>>>> 4) From Start > Programs > Microsoft Visual Studio 2008 > Visual
>>>>>>> Studio
>>>>>>> Tools , I opened Visual Studio 2008 Command Prompt.
>>>>>>> 5) Ran vcvarsall.bat to set up the rest of the variables.
>>>>>>> 6) With ISimpleDOMNode.idl in the same dir as vcvarsall.bat, I
>>>>>>> entered
>>>>>>> midl ISimpleDOMNode.idl
>>>>>>>
>>>>>>> I've attached the only generated files. This includes the
>>>>>>> ISimpleDOMNode.idl
>>>>>>> file for reference. No TLB, just .c files.
>>>>>>>
>>>>>>> Would it be possible for me to just create a C++ project in VS.net
>>>>>>> using
>>>>>>> these C files to make my own class lib? This shouldn't be necessary,
>>>>>>> but
>>>>>>> I
>>>>>>> don't know what else to try.
>>>>>>>
>>>>>>> Arg,
>>>>>>>
>>>>>>> Bryan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --------------------------------------------------------------------------------
>>>>>>> Bryan Garaventa
>>>>>>> Senior Accessibility Engineer
>>>>>>> SSB + BART Group
>>>>>>> [hidden email]
>>>>>>> www.SSBBartGroup.com
>>>>>>> Accessibility-On-Demand
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Steve Lee" <[hidden email]>
>>>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>>>> Cc: "dev-accessibility Firefox"
>>>>>>> <[hidden email]>
>>>>>>> Sent: Monday, July 21, 2008 11:09 PM
>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>
>>>>>>>
>>>>>>>> Sorry If I didn't make it clear but you should run a batch file
>>>>>>>> called
>>>>>>>> something like vcvars.bat in you command prompt first. This will
>>>>>>>> set
>>>>>>>> up the environment variable so the compilers find the correct
>>>>>>>> files.
>>>>>>>> This sounds like the proble. You should nto have to copy files and
>>>>>>>> that can cause confusion due to the way the compiler searches for
>>>>>>>> included files. The exact file name various with the version of the
>>>>>>>> tools you use. The only complication comes as you often have set
>>>>>>>> things up for both the VC and SDK.
>>>>>>>>
>>>>>>>> If you use the Mozilla Build system it should sort this out for you
>>>>>>>> and gives you a nice UNIX like shell.
>>>>>>>>
>>>>>>>> Steve
>>>>>>>>
>>>>>>>> 2008/7/22 Bryan Garaventa <[hidden email]>:
>>>>>>>>> Actually, this output doesn't look like C++ header code, but
>>>>>>>>> rather
>>>>>>>>> an
>>>>>>>>> error
>>>>>>>>> log from the midl compiler.
>>>>>>>>>
>>>>>>>>> I've attached the generated files from midl.exe from the cmd
>>>>>>>>> prompt
>>>>>>>>> in
>>>>>>>>> case
>>>>>>>>> anyone would like to take a look, and hopefully, can provide a
>>>>>>>>> totally
>>>>>>>>> brilliant insight that can restore my faith in Microsoft products
>>>>>>>>> as
>>>>>>>>> a
>>>>>>>>> whole
>>>>>>>>> in one fell swoop?
>>>>>>>>>
>>>>>>>>> I can't say I understand it. This time I used the 2008 Vista SDK
>>>>>>>>> to
>>>>>>>>> make
>>>>>>>>> sure I have the most recent files.
>>>>>>>>>
>>>>>>>>> Also, I used the /I switch to designate the include folder, for
>>>>>>>>> instance
>>>>>>>>> midl /I "C:\Program Files\Microsoft SDKs\Windows\v6.0\Include"
>>>>>>>>> ISimpleDOMNode.idl
>>>>>>>>> So that none of the includes could be accidentally omitted.
>>>>>>>>>
>>>>>>>>> I didn't get any errors in the command prompt, but in the .h file,
>>>>>>>>> it
>>>>>>>>> says
>>>>>>>>> that I need a more recent version of rcndr.h and that I missing
>>>>>>>>> windows.h,
>>>>>>>>> which is confusing. This is a 2008 update package so it should
>>>>>>>>> contain
>>>>>>>>> the
>>>>>>>>> latest header files, I would assume anyway. Also, I checked the
>>>>>>>>> include
>>>>>>>>> directory and it does contain a windows.h file in the same folder
>>>>>>>>> as
>>>>>>>>> objidl.idl, so I'm not sure why it would be saying it's not there.
>>>>>>>>>
>>>>>>>>> I wonder if MS has ever heard of the KISS principle...
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>> Bryan Garaventa
>>>>>>>>> Senior Accessibility Engineer
>>>>>>>>> SSB + BART Group
>>>>>>>>> [hidden email]
>>>>>>>>> www.SSBBartGroup.com
>>>>>>>>> Accessibility-On-Demand
>>>>>>>>>
>>>>>>>>> ----- Original Message ----- From: "Bryan Garaventa"
>>>>>>>>> <[hidden email]>
>>>>>>>>> To: "dev-accessibility Firefox"
>>>>>>>>> <[hidden email]>
>>>>>>>>> Cc: "dev-accessibility Firefox"
>>>>>>>>> <[hidden email]>
>>>>>>>>> Sent: Monday, July 21, 2008 1:24 PM
>>>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Thanks, that's no problem.
>>>>>>>>>>
>>>>>>>>>> I'm using cmd to access midl.exe, using the docs at
>>>>>>>>>> http://msdn.microsoft.com/en-us/library/aa367064(VS.85).aspx as a
>>>>>>>>>> reference.
>>>>>>>>>>
>>>>>>>>>> Many of the included files appear to be spread around various
>>>>>>>>>> directories
>>>>>>>>>> though, so it took me a while to track the errors enough to
>>>>>>>>>> gather
>>>>>>>>>> all
>>>>>>>>>> of
>>>>>>>>>> these files into one main directory. This includes cl.exe and the
>>>>>>>>>> other
>>>>>>>>>> referenced dll. So far, I've been using those files found in the
>>>>>>>>>> Program
>>>>>>>>>> Files\Microsoft Visual Studio 8 folder. After installing VS9, I
>>>>>>>>>> found
>>>>>>>>>> two
>>>>>>>>>> objidl.idl files, one in the Smart Devices folder, and in the
>>>>>>>>>> Smart
>>>>>>>>>> Phone
>>>>>>>>>> folder, but I couldn't find any references to determine if these
>>>>>>>>>> files
>>>>>>>>>> are
>>>>>>>>>> device dependant. I'm not having much luck finding any docs that
>>>>>>>>>> really
>>>>>>>>>> explain how Midl is supposed to be used, and which files are
>>>>>>>>>> directly
>>>>>>>>>> relevant for a standard Win32 environment.
>>>>>>>>>>
>>>>>>>>>> I did try the compilation without the /nocpp switch, and also
>>>>>>>>>> leaving
>>>>>>>>>> out
>>>>>>>>>> the /tlb switch as well. The results were weird. Apparently, the
>>>>>>>>>> default
>>>>>>>>>> switches should automatically generate the C headers and the TLB
>>>>>>>>>> within
>>>>>>>>>> the
>>>>>>>>>> same directory. Well, the C headers appear to generate fine, no
>>>>>>>>>> errors
>>>>>>>>>> appear within the command prompt during the compilation. This is
>>>>>>>>>> using
>>>>>>>>>> the
>>>>>>>>>> same objidl.idl file as mentioned before, located in the Program
>>>>>>>>>> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Include folder.
>>>>>>>>>> However,
>>>>>>>>>> no
>>>>>>>>>> TLB file is generated. Only when I disable the C processor using
>>>>>>>>>> /no_cpp
>>>>>>>>>> or
>>>>>>>>>> /nocpp, does this syntax error occur.
>>>>>>>>>>
>>>>>>>>>> I'm hoping that I'm missing something simple, like not changing
>>>>>>>>>> the
>>>>>>>>>> correct
>>>>>>>>>> info in the ISimpleDOMNode.idl file, which would be a happy
>>>>>>>>>> mistake
>>>>>>>>>> since
>>>>>>>>>> I
>>>>>>>>>> wouldn't believe I was actually going nuts.
>>>>>>>>>>
>>>>>>>>>> Just in case, these are the lines I changed within the
>>>>>>>>>> ISimpleDOMNode.idl
>>>>>>>>>> file based on Aaron's discovery earlier. (Changing all of the
>>>>>>>>>> iDISP
>>>>>>>>>> constants from negative to positive values.)
>>>>>>>>>>
>>>>>>>>>> const long DISPID_NODE_NODEINFO   = 5900;
>>>>>>>>>> const long DISPID_NODE_ATTRIBUTES = 5901;
>>>>>>>>>> const long DISPID_NODE_ATTRIBUTESFORNAMES = 5902;
>>>>>>>>>> const long DISPID_NODE_COMPSTYLE  = 5903;
>>>>>>>>>> const long DISPID_NODE_COMPSTYLEFORPROPS = 5904;
>>>>>>>>>> const long DISPID_NODE_LANGUAGE = 5905;
>>>>>>>>>>
>>>>>>>>>> Could this be the problem?
>>>>>>>>>>
>>>>>>>>>> I appreciate the help, but it's no rush.
>>>>>>>>>>
>>>>>>>>>> Best wishes,
>>>>>>>>>>
>>>>>>>>>> Bryan
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --------------------------------------------------------------------------------
>>>>>>>>>> Bryan Garaventa
>>>>>>>>>> Senior Accessibility Engineer
>>>>>>>>>> SSB + BART Group
>>>>>>>>>> [hidden email]
>>>>>>>>>> www.SSBBartGroup.com
>>>>>>>>>> Accessibility-On-Demand
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ----- Original Message ----- From: "Steve Lee"
>>>>>>>>>> <[hidden email]>
>>>>>>>>>> To: "Bryan Garaventa" <[hidden email]>
>>>>>>>>>> Cc: "dev-accessibility Firefox"
>>>>>>>>>> <[hidden email]>
>>>>>>>>>> Sent: Sunday, July 20, 2008 3:08 AM
>>>>>>>>>> Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> Reposting to list
>>>>>>>>>>>
>>>>>>>>>>> Hi Bryan, sounds painfull, I just spent ages tryign to get a
>>>>>>>>>>> mozilla
>>>>>>>>>>> build going and have run out of time to look more till next week
>>>>>>>>>>> :-(
>>>>>>>>>>>
>>>>>>>>>>> One thing are you sure /nocpp is correct? Something may want the
>>>>>>>>>>> C
>>>>>>>>>>> pre
>>>>>>>>>>> processor, which might be why it's barfing in the comments.
>>>>>>>>>>> Thats
>>>>>>>>>>> a
>>>>>>>>>>> pretty basic syntax error indicating it really confused with the
>>>>>>>>>>> source. I'm also not sure you need /tlb either.
>>>>>>>>>>>
>>>>>>>>>>> You should check that INCLUDE is set correctly, it might not be
>>>>>>>>>>> using
>>>>>>>>>>> the right files or your local copies.
>>>>>>>>>>> Are you build in the MinGW environment or cmd? If you use
>>>>>>>>>>> start-msvcN.bat it should be all set up for you (though I just
>>>>>>>>>>> had
>>>>>>>>>>> to
>>>>>>>>>>> patch it for VC9Express)
>>>>>>>>>>>
>>>>>>>>>>> Steve
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> dev-accessibility mailing list
>>>>>>>>>> [hidden email]
>>>>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> dev-accessibility mailing list
>>>>>>>>> [hidden email]
>>>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Steve Lee
>>>>>>>> Open Source Assistive Technology Software and Accessibility
>>>>>>>> fullmeasure.co.uk
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>> _______________________________________________
>>>>>>> dev-accessibility mailing list
>>>>>>> [hidden email]
>>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> dev-accessibility mailing list
>>>>>> [hidden email]
>>>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Steve Lee
>>>>> Open Source Assistive Technology Software and Accessibility
>>>>> fullmeasure.co.uk
>>>>
>>>> _______________________________________________
>>>> dev-accessibility mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-accessibility
>>>>
>>>
>>>
>>>
>>> --
>>> Steve Lee
>>> Open Source Assistive Technology Software and Accessibility
>>> fullmeasure.co.uk
>>
>> _______________________________________________
>> dev-accessibility mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-accessibility
>>
>
>
>
> --
> Steve Lee
> Open Source Assistive Technology Software and Accessibility
> fullmeasure.co.uk

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Steve Lee-3
Bryan, I have doubts as I expect it uses dispinterface access, however
here is a tlb built from ISympleDOMNode. I have no idea if it is what
you need but markefile rule I built it with is

        $(MIDL) $(MIDL_FLAGS) -I $(srcdir) -Oicf $(srcdir)/ISimpleDOMNode.idl
/tlb $(srcdir)/ISimpleDOMNode.tlb

which may give you clues how to build it yourself.

Sorry I can't be more help at the moment.

--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility
Reply | Threaded
Open this post in threaded view
|

Re: Not managing to build .tlb for SimpleDOMNode.idl

Bryan Garaventa-2
That's awesome! I believe I've found a way to add this tlb to the project,
which is the first step at any rate. Thank you so much, all of your help has
been invaluable.
Best wishes,
Bryan




--------------------------------------------------------------------------------
Bryan Garaventa
Senior Accessibility Engineer
SSB + BART Group
[hidden email]
www.SSBBartGroup.com
Accessibility-On-Demand

----- Original Message -----
From: "Steve Lee" <[hidden email]>
To: "Bryan Garaventa" <[hidden email]>
Cc: "dev-accessibility Firefox" <[hidden email]>
Sent: Friday, July 25, 2008 3:45 AM
Subject: Re: Not managing to build .tlb for SimpleDOMNode.idl


> Bryan, I have doubts as I expect it uses dispinterface access, however
> here is a tlb built from ISympleDOMNode. I have no idea if it is what
> you need but markefile rule I built it with is
>
> $(MIDL) $(MIDL_FLAGS) -I $(srcdir) -Oicf $(srcdir)/ISimpleDOMNode.idl
> /tlb $(srcdir)/ISimpleDOMNode.tlb
>
> which may give you clues how to build it yourself.
>
> Sorry I can't be more help at the moment.
>
> --
> Steve Lee
> Open Source Assistive Technology Software and Accessibility
> fullmeasure.co.uk
>


--------------------------------------------------------------------------------


> _______________________________________________
> dev-accessibility mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-accessibility
>

_______________________________________________
dev-accessibility mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-accessibility