Re[2]: new app: fcd-1.0
Thanks for looking at the code. I was trying to get it working under straight Win32, which doesn't support the opendir/readdir API as far as I can tell. Unfortunately, implementation under Win32 given the primitive shell looks ugly enough to not be worth it. -Wade Friday, March 15, 2002, 12:40:04 AM, you wrote: CV On Thu, Mar 14, 2002 at 06:03:23PM -0800, Wade Brainerd wrote: Anyway, it's my first real unix-style app so I'm anxious for feedback. It compiles on Solaris, MacOS X and Cygwin (and probably others, let me know if you try compiling it somewhere else). CV I had a quick glance into the source code and I wonder why you CV implemented your own opendir()/readdir(). It's in the API of all CV the above OSes. CV Corinna -- 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/
new app: fcd-1.0
Hi all, Just writing to announce my first Unix/Cygwin app, it's a tiny utility that makes changing directories faster. It tries to expand each 'step' of a path as a wildcard from both the current directory and also from each directory in an environment variable. For example, if you have ~/my_web_server.com/long-path-150 and ~/ is in your SEARCH environment, you can type (from any folder on your machine): fcd my/*150 and it will take you there. The program is implemented to just print out the name of the path it finds, and it's wired into the shell via a function on bash and an alias on tcsh. Anyway, it's my first real unix-style app so I'm anxious for feedback. It compiles on Solaris, MacOS X and Cygwin (and probably others, let me know if you try compiling it somewhere else). The link to the latest version can be found at http://www.wadeb.com/, the direct link is: http://www.wadeb.com/fcd-1.0.tar.gz Thanks! Wade Brainerd [EMAIL PROTECTED] -- 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/
changing the working directory from a c program
Hi all, I'm aware that this is a troublesome issue and hard to do on all platorms (Win32, various Unix's) but I'm asking anyway :) Under Cygwin, is there any way for a C program to change the current working directory of the shell that executed it? My best bet so far is to wrap the C program in a script Thanks, Wade Brainerd adebcom -- Unsubscribe info: http://cygwincom/ml/#unsubscribe-simple Bug reporting: http://cygwincom/bugshtml Documentation: http://cygwincom/docshtml FAQ: http://cygwincom/faq/
Re: DirectX8/DirectInput + cygwin
Sounds like a DEF file problem. Functions in DLLs use a different naming convention from C++ mangled names and C identifiers, usually: FunctionName@ArgSize ...where ArgSize is the total size of all the parameters arguments, say for example a function MyFunction taking a single pointer as a parameter would be MyFunction@4. .DEF files are what Visual C++ uses to associate functions in header files with functions in DLLs, I'm not sure what the Cygwin equivalents are. In fact, I know almost nothing about Cygwin but a lot about Windows DLLs, but I thought this might put you on the right track ;) -Wade Wednesday, February 06, 2002, 2:22:09 AM, you wrote: DC Hello there, DC I've searched the archives high and low and can't seem to find a solution to DC my problem. DC When compiling a DirectInput8 function such as DirectInput8Create() I get an DC error linking: DC Unable to resolve DirectInput8Create@20 DC I am linking directly with the .lib files supplied by Microsoft, and all the DC Directx8 GUID references seem to link fine so does anybody have any idea DC what the problem might be? DC What version of DirectX are the directX libs in /usr/libs/ created for? DC As an extra note, gcc v3.00-3.02 won't compile unknwn.h without an internal DC compiler error, but v3.03 seems fine. DC Regards DC - DC Q-Games, Dylan Cuthbert. DC http://www.q-games.com DC -- DC Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple DC Bug reporting: http://cygwin.com/bugs.html DC Documentation: http://cygwin.com/docs.html DC FAQ: http://cygwin.com/faq/ -- 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/
Re[2]: DirectX8/DirectInput + cygwin
By the way, you can access the DirectX C interfaces (or any COM interface for that matter) from C++ by #defining CINTERFACE before including the header containing the interface. Also, you don't have to use lpVtable, you can always use the macros they provide (your preference). -Wade Wednesday, February 06, 2002, 3:11:14 AM, you wrote: B Getting DirectX to work from cygwin GCC essentially can't be done from C++, B but can be done from C. It can't be done from C++ because of the way COM B virtual tables work. GCC can't clone Visual C++'s method because Microsoft B holds a U.S. patent on their exact method. Just try using MFC from GCC and B you'll know exactly what I mean. B In C, the virtual table system is done by actually creating the vtable B structure in the header file, so this isn't a problem. If you modify the B DirectX header files, you could fix this for C++, but you'd have to do -lpVtable all the time, like in C. B GCC, or rather binutils, can't handle the Microsoft import library format. B binutils of course has its own, so you could make your own from the DLL. B If import libraries don't work, you could always GetProcAddress on B DirectInputCreate8 after loading dinput8.dll. Then the problem becomes how B to get to the weird global functions (D3DX matrix stuff, for instance). B -- Barubary B - Original Message - B From: Dylan Cuthbert [EMAIL PROTECTED] B To: Cygwin@Cygwin. Com [EMAIL PROTECTED] B Sent: Wednesday, February 06, 2002 2:22 AM B Subject: DirectX8/DirectInput + cygwin When compiling a DirectInput8 function such as DirectInput8Create() I get B an error linking: Unable to resolve DirectInput8Create@20 B -- B Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple B Bug reporting: http://cygwin.com/bugs.html B Documentation: http://cygwin.com/docs.html B FAQ: http://cygwin.com/faq/ -- 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/
