headers
andy younger | 7 Feb 2002 01:30
Picon
Picon

Re: DirectX8/DirectInput + cygwin

Peter Puck has already made bindings for Direct X 8. The site appears to 
be down at the moment, but if you google for

dx8 "Peter Puck"

you can probably find them, I believe these are MingW bindings, but they 
work fine with cygwin.

Contrary to popular belief you can use the COM/C++ bindings. Gcc's 
default way of doing thunking is different than visual C's, but if you 
use the compiler option -fvtable-thunks it uses the vtable method. Due 
to this being a ABI change, you will need to build all your source files 
with this. This obviously does not fix the name mangling 
incompatibilities with Visual C, but on a COM interface such as DX, this 
does not matter.

The biggest problem you will have are with DirectShow, and the D3DX 
libraries.

DirectShow (or whatever it is called these days) has a C++ interface to 
it, and as such will only work with visual C's mangling scheme. So no 
joy there..

With D3DX, the problem is that the libraries are statically linked, and 
use Visual C++'s name mangling scheme for most of the internal symbols. 
This leaves them somewhat useless for any compiler rather than Visual C. 
There are 2 solutions to this.

	- don't use them, they are convenient, but not essential to DX programming.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Warren Young | 7 Feb 2002 01:51
Favicon

Re: /proc (was: Re: /dev/registry)

Chris January wrote:
> 
> I'll probably add some entries to /proc - ones commonly found on UNIX
> platforms maybe. Anyone have any favourites they wish to see?

I don't know about "favorite", but the only one that's even close to
standardized across Unices is /proc/≤pid>.  And even that is nonstandard
everywhere: it's a bunch of text files on Linux, and a bunch of binary
files by different names under recent SysVR4.  (Or SVR5, as Caldera nee
SCO insists on calling it.)

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
Permalink | Reply | 0 comments |
headers
Chris January | 7 Feb 2002 01:56

Re: /proc (was: Re: /dev/registry)

> > 1. it's difficult to accidentally cat to a key considering the length of
the
> > names  -
> >
/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/S
> > hell\ Extensions/Approved/\{BDEADF00-C265-11d0-BCED-00A0C90AB50F\} is a
bit
> > hard to type in by accident...
At the moment, I have called the default key value, "(default"), the same as
regedit. Does anyone have any objections to this (and if so a better
suggestion)? The brackets can't be typed into bash without being quoted;
this might become a bit of a pain.

Regards
Chris

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
Permalink | Reply | 1 comment |
headers
Stephan Mueller | 7 Feb 2002 02:00
Picon
Favicon

RE: /proc (was: Re: /dev/registry)

Another suggestion (I won't presume to say better):

.reg files refer to this value as  <at> .  E.g.

	REGEDIT4
	
	[HKEY_CURRENT_USER\AppEvents\Schemes]
	 <at> =".current"

stephan();

-----Original Message-----
From: Chris January [mailto:chris <at> atomice.net] 
Sent: Wednesday, February 06, 2002 4:56 PM
To: cygwin <at> cygwin.com
Subject: Re: /proc (was: Re: /dev/registry)

> > 1. it's difficult to accidentally cat to a key considering the 
> > length of
the
> > names  -
> >
/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersi
on/S
> > hell\ Extensions/Approved/\{BDEADF00-C265-11d0-BCED-00A0C90AB50F\} 
> > is a
bit
> > hard to type in by accident...
At the moment, I have called the default key value, "(default"), the
same as regedit. Does anyone have any objections to this (and if so a
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dylan Cuthbert | 7 Feb 2002 02:22
Favicon

Re: DirectX8/DirectInput + cygwin

If this is the case, does this mean the problem I'm getting with
DirectInput8Create <at> 20 not being found is due to differences in C++ name
mangling as another poster mentioned only C libraries being able to link.

Linking directly with the DirectX SDK .lib files cleared up all the
unresolved errors apart from just this single one, but I'm only calling a
few directx function calls as a test so presumably I'll come across the same
problem when I start using more function calls.

Thanks for the help, I feel I'm getting a few starting points to try out.

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com

----- Original Message -----
From: "Christopher Faylor" <cygwin <at> cygwin.com>
To: <cygwin <at> cygwin.com>
Sent: Thursday, February 07, 2002 3:18 AM
Subject: Re: DirectX8/DirectInput + cygwin

> On Wed, Feb 06, 2002 at 07:10:49PM +0100, Pavel Tsekov wrote:
> >Christopher Faylor wrote:
> >>On Wed, Feb 06, 2002 at 12:11:58PM +0100, Pavel Tsekov wrote:
> >>>Dylan Cuthbert wrote:
> >>>>I am linking directly with the .lib files supplied by Microsoft, and
> >>>>all the Directx8 GUID references seem to link fine so does anybody
have
> >>>>any idea what the problem might be?
> >>>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dylan Cuthbert | 7 Feb 2002 02:31
Favicon

Re: DirectX8/DirectInput + cygwin


Thanks folks - I found a mirror for the dx8 libs on Peter Puck's web site -

http://rain.prohosting.com/urebel/download.html

Also, Peter Puck's web site is down at the moment - hopefully it will come
back up:
it is:
http://sites.netscape.net/ptrpck/directx.htm

I'll try installing these today and see if I can make some progress, thanks
to everyone for their quick response!  I'll send a DirectX section to the
FAQ maintainer once I get all this working as a kind of payback.

Regards

---------------------------------
Q-Games, Dylan Cuthbert.
http://www.q-games.com

----- Original Message -----
From: "andy younger" <andy <at> snoogie.demon.co.uk>
To: "Barubary" <barubary <at> cox.net>
Cc: <cygwin <at> cygwin.com>
Sent: Thursday, February 07, 2002 9:30 AM
Subject: Re: DirectX8/DirectInput + cygwin

> Peter Puck has already made bindings for Direct X 8. The site appears to
> be down at the moment, but if you google for
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael A Chase | 7 Feb 2002 02:37
Picon

Re: /proc (was: Re: /dev/registry)

Just another log on the fire, the Perl registry modules use "" for the
(default) value.

Even so, I'd lean toward " <at> " since it's hard to name a file "".

You may need to have an ioctl() to change the key separator.  '\' would
probably be ok, but difficult.  The problem with '/' might make it hard to
handle the cygwin mount tables.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.
----- Original Message -----
From: "Stephan Mueller" <smueller <at> microsoft.com>
To: "Chris January" <chris <at> atomice.net>; <cygwin <at> cygwin.com>
Sent: Wednesday, February 06, 2002 17:00
Subject: RE: /proc (was: Re: /dev/registry)

Another suggestion (I won't presume to say better):

.reg files refer to this value as  <at> .  E.g.

REGEDIT4

[HKEY_CURRENT_USER\AppEvents\Schemes]
 <at> =".current"

stephan();
(Continue reading)

Permalink | Reply | 0 comments |
headers
Charles Wilson | 7 Feb 2002 02:55
Picon
Favicon

Re: cvs: Terminated with fatal signal 6

Just a hunch: do the openoffice sources contain files (within the same 
directory) whose names differ only in case?  If so, then cygwin cvs will 
have problems...

--Chuck

Volker Quetschke wrote:

> Hi!
> 
> I just tried to download the Openoffice sources with cvs running on 
> cygwin (1.3.9, everything updatet, all binary mounts) / Windows 2K.
> 
> $export CVSROOT=":pserver:anoncvs <at> anoncvs.openoffice.org:/cvs"
> 
> $cvs login
> ... Password: anoncvs
> 
> $cvs checkout -r OpenOffice341C OpenOffice
> cvs: lock.c:177: lock_name: Assertion `(__extension__ 
> (__builtin_constant_p ( strlen (CVSroot_directory)) && 
> ((__builtin_constant_p (repository) && strlen (repository) < ((size_t) ( 
> strlen (CVSroot_directory)))) || (__builtin_constant_p
> [stuff deleted]
> CVSroot_directory)))); }) : strncmp (repository, CVSroot_directory, 
> strlen (CVSroot_directory)))) == 0' failed.
> Terminated with fatal signal 6
> 
> I write this to the cygwin list, because when I try the commands given
> above on a sun solaris machine everything is OK and cvs starts to download.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Billinghurst, David (CRTS | 7 Feb 2002 03:03
Favicon

RE: cvs: Terminated with fatal signal 6

cygwin cvs (on win2k) copes with this ok.  It happens with gcc and maxima sources.  It just overwrites on file
and complains.

-----Original Message-----
From: Charles Wilson [mailto:cwilson <at> ece.gatech.edu]
Sent: Thursday, 7 February 2002 12:56 
To: Volker Quetschke
Cc: cygwin <at> cygwin.com
Subject: Re: cvs: Terminated with fatal signal 6

Just a hunch: do the openoffice sources contain files (within the same 
directory) whose names differ only in case?  If so, then cygwin cvs will 
have problems...

--Chuck

Volker Quetschke wrote:

> Hi!
> 
> I just tried to download the Openoffice sources with cvs running on 
> cygwin (1.3.9, everything updatet, all binary mounts) / Windows 2K.
> 
> $export CVSROOT=":pserver:anoncvs <at> anoncvs.openoffice.org:/cvs"
> 
> $cvs login
> ... Password: anoncvs
> 
> $cvs checkout -r OpenOffice341C OpenOffice
> cvs: lock.c:177: lock_name: Assertion `(__extension__
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kent Watsen | 7 Feb 2002 03:17

dlopen(0, RTLD_LAZY) doesn't work?


Hi,

I've read the mailing list archives and searched google trying
to figure out how to get the following program to work.  All
you have to do is save it to a file (foo.c), compile (gcc foo.c),
and run - I always get "dlsym() failed."

Note, I have tried many variations of extern and _declspec
as well as looking for "_foo" in addition to "foo" ("nm a.exe |
grep foo" returned "0040104c T _foo"...

Here is the code - help would be greatly appreciated - thanks!

#include <stdio.h>
#include <dlfcn.h>
#include <windows.h>

extern __declspec(dllexport) void foo(void)
{
    printf("hello\n");
}

int main(int argc, char *argv[])
{
    void* dl    = NULL;
    void* func = NULL;

    dl = dlopen(0 , RTLD_LAZY);
    if (dl == NULL) {
(Continue reading)

Permalink | Reply | 3 comments |

Gmane