From: Lloyd D. <ll...@ga...> - 2001-07-30 22:05:06
|
Chris Marshall wrote: > > Lloyd - > > I'm going to stick my two cents in, ... i must admit that, though my name, i am french, and i understand the above line is just an expression not related to mingw, anyway, what does it mean ? > Assuming that you are correct that SafeArrayCreateEx() is a part > of the oleaut32.dll, then it seems to me that you need to have an > oleaut32.lib and an oleaut32.h somewhere ... > perhaps obtained from the Microsoft SDK? in fact oleaut32.dll is a standart DLL found in C:\WINNT\System32\oleaut32.dll (not specifically shipped with a dev env) it seems that SafeArrayCreateEx is new, as i have bought, in the beginning of 98, Visual C++ 5, which is shipped with OLEAUTO.H which has a definition for 'SafeArrayCreate' but not for 'SafeArrayCreateEx' > Otherwise, you might have to build a libary from the .DLL by > creating a .DEF > file and then using dlltool (what I went through a couple of weeks > ago). I don't see how that procedure solves the problem of the > missing .h file, however. yeah, ... the problem is that i allready try to download microsoft SDK just a few week ago, but this download a 64 bit version of visual studio, CL compiler and header. it don't work on my machine and it is not shiped with ole*.h headers. (maybe i missed something ?) |
From: Chris M. <nin...@ho...> - 2001-07-30 23:14:54
|
Lloyd - Je ne parle pas en francias bien, mais j'essayerai. J'ai obtenu l'aide de http://babelfish.altavista.com. L'expression de "to stick my two cents in" pourrais également être écrit "je voudrais ajouter mes deux cents à cette discussion." ("I wish to add my two cents to this discussion.") Un "cent" est la plus petite piece en le dollar, 1/100th. Je pense que il est equivalent au "centimme" (spelling?) en le franc francais? Il signifie que l'information que je souhaite ajouter pourrait être de petite valeur, et je sais cela, mais je vais le dire de toute façon. A tout Chris ----Original Message Follows---- Chris Marshall wrote: > > Lloyd - > > I'm going to stick my two cents in, ... i must admit that, though my name, i am french, and i understand the above line is just an expression not related to mingw, anyway, what does it mean ? _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |
From: niceguy <ni...@ab...> - 2001-07-31 00:59:31
|
---------- Original Message ---------------------------------- From: "Lloyd Dupont" <ll...@ga...> Date: Tue, 31 Jul 2001 00:07:47 +0200 >Chris Marshall wrote: >> >> Lloyd - >> >> I'm going to stick my two cents in, >... i must admit that, though my name, i am french, and i understand > the above line is just an expression not related to mingw, anyway, > what does it mean ? The term 'two cents' refers to currency, and two cents in American currency isn't worth much. So, to say you are 'putting your two cents in' means that you are going to offer some information, but it may not be very useful. > > >> Assuming that you are correct that SafeArrayCreateEx() is a part >> of the oleaut32.dll, then it seems to me that you need to have an >> oleaut32.lib and an oleaut32.h somewhere ... >> perhaps obtained from the Microsoft SDK? >in fact oleaut32.dll is a standart DLL found in >C:\WINNT\System32\oleaut32.dll >(not specifically shipped with a dev env) > >it seems that SafeArrayCreateEx is new, as i have bought, in the >beginning of 98, Visual C++ 5, which is shipped with OLEAUTO.H which >has a definition for 'SafeArrayCreate' but not for 'SafeArrayCreateEx' Generally, the functions with 'Ex' represent some difference between Windows 9x and Window NT/2000. If you aren't targeting the 9x systems, the function without the 'Ex' is usually preferred. The SDK documentation at the Microsoft site is very useful for determining which version should be used for which platform. I have some COM code on my NT machine that uses 'SafeArrayCreate' and Mingw has no problems understanding it. Jim S. |
From: Chris H. <pop...@so...> - 2001-07-31 01:28:57
|
>Subject: Re: [Mingw-users] about COM > From: "niceguy " <ni...@ab...> > Date: Mon, 30 Jul 2001 20:59:11 -0400 > To: <min...@li...> > >---------- Original Message ---------------------------------- >Generally, the functions with 'Ex' represent some difference between Windows 9x and Window NT/2000. If you aren't targeting the 9x systems, the function without the 'Ex' is usually preferred. The SDK documentation at the Microsoft site is very useful for determining which version should be used for which platform. I have some COM code on my NT machine that uses 'SafeArrayCreate' and Mingw has no problems understanding it. That is not quite true. Most of the 'Ex'-functions in the Windows API is improved functions simular to the ones without the 'Ex'. They came around when Windows 95 got out. So actually they are the difference between Windows 3x and Windows 4x. The difference to the NT platforms is the 'A' and 'W' functions. They are both in Windows 95 for compatibility issues, but the major part of the 'W' in Windows 95 does nothing. I wonder why the Unicode implementation wasn't in Windows 98. The were available from the NT4 kernel, so I cannot find a reason why they still are unimplementet in ME. I know this is OT but have any of you ever lined up some of the latest Windows names? Check this one: CE+ME+NT equals what? "Windows CEMENT" :-) Regards Chris Hansen |
From: Joerg B. <jo...@sq...> - 2001-08-01 08:28:55
|
Hi MinGW users / developers! "Paul G." wrote: > > On 30 Jul 2001, at 20:59, the Illustrious niceguy wrote: > > [...] In > this case the topic is COM, a Microsoft Specific method of handling > things that don't really exist except as they are defined within the > context of the source code itself (C or C++). In fact, COM is nothing > more than a collection of software constructs which are required for > DirectX development. Microsoft calls them Common Object Modules (I > believe). Not quite: "COM" stands for "Component Object Model", AFAIR. It is a MS-specific way of defining interfaces to software, storing and "publishing" these definitions in a computer, and allowing other software to query these interfaces and then call the software implementing them. In other words: It is a way to manage the interfaces in client-server software architectures and allow run-time combination (depending on the existence of the server components) of such systems. (The alternative to this as an open standard should be "CORBA", as I understand it.) The extension to COM is "DCOM", "Distributed COM", where all this works in a network (as opposed to a single machine). (I had some colleagues porting that MS DCOM stuff to some Unix platforms, this is "Entire X" of Software AG, Germany. The objective is to integrate Win32 and other platforms in large client-server applications, including MS tools as graphic frontends to mainframe legacy commercial applications.) However, I have no info about whether (and how) "gcc" (and other MinGW software) supports COM and/or DCOM, and what the necessary MS libraries are to use COM/DCOM. It may well be that "DirectX" is implemented using COM, but this is just one application - there are more. > COM-Object is not to be confused with COM-Port as they are > in fact two entirely different, and largely unrelated, concepts. IMHO: s/largely/totally/ Regards, Joerg Bruehe -- Joerg Bruehe, SQL Datenbanksysteme GmbH, Berlin, Germany (speaking only for himself) mailto: jo...@sq... |