Where Can I Get Windows.h For Mac
Jan 3, 2006 - Hi all, I was looking at porting some of windows code to MAC. I was browsing through window.h header file and I came upon some definitions.
I was able to build and run the Darwine Xcode template! My PATH setting above was working in the Makefile. It actually was a different error later.
I added the following to Makefile: (Remember I'm on Intel, so you may need to change i386 to your architecture ppc, ppc4, x8664) PATH = $PATH:/Developer/Tools:/usr/libexec/gcc/darwin/i386:/usr/bin There were also warnings about not finding the path /usr/lib/wine I don't know if Darwine (or Darwine SDK) installed this or is missing this library path or if I overwrote it with WineHQ versions, but I (re)installed winehq.com wine-0.9.33 next. WineHQ had minor install problems for me. If./tools/wineinstall doesn't work for you, try from an X11 window (not the standard Mac OS X Terminal window - so you need to have X11 installed)./configure make depend && make make install (this last make requires root or sudo) Then I was able to replace in the Makefile LIBRARYPATH = -L/usr/lib/wine with LIBRARYPATH = -L/mypathto/wine-0.9.33/dlls Don't forget the earlier changes in this thread (Appending to INCLUDEPATH -I/Developer/Headers/Wine/include/wine/windows and CEXTRA and CXXEXTR for i386 or your architecture) I think that's it. Click Build from Xcode. Succeeded baby! No Warnings and No Errors Then I ran it in an X11 window from /mypathto/wine-0.9.33/ with./wine /mypathto/darwinehelloworld.exe.so Good Luck!
Hey Mac, Thanks for your detailed report. The bug that Jim White referenced is independent of the SDK. That is very interesting that its not finding windows.h. The SDK should be ready to go but if i'm not mistaken Apple has made some big changes to xCode and honestly I haven't had the time to sit down and address the sdk. I know there are problems with it regarding bigger programs and Ive spent a few hours here and there but haven't gotten very far. Regardless though the template project should compile and work fine. One thing you might want to check is your.tcshrc (i think that's right ) or.bash file and setenv to the include path you referenced.
Try seeing if you can do a make compile from the command line for the sample project that's included with the xCode template. I'd be curious as to what its trying to do. I will try to get back to you as soon as I can, but if you don't hear from me for a few days, don't worry I didn't forget. Thanks, Sanjay. This works in Xcode: Change: #include To: #include '/Developer/Headers/Wine/include/wine/windows/windows.h' So explicitly listing the full path in all headers may be a painful workaround. But I edited my Makefile's INCLUDEPATH to include /Developer/Headers/Wine/include/wine/windows and get a little further: make gcc -c -DWINE -DREENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -gstabs+ -Wpointer-arith -ffixed-r13 -no-cpp-precomp -Dpowerpc -I.
Sorry, gmail did not keep this in the same label, probably because I editted the subject. As I said before, I am on an Intel Mac Mini, so in my case I also changed 2 occurrences of powerpc in the Makefile to i386 in CEXTRA and CXXEXTRA, and now I only have 1 error and no warnings. The CONTEXT. redefinitions went away.
Where Can I Get Windows.h For Mac Download
Now make cannot find winegcc I am trying to add PATH=$PATH:/Developer/Tools to the Makefile in the hopes make will look for executables in this new PATH, but no luck so far. If you know how to tell make to search a particular path for executables, please let me know. By the way, I first decided to edit the Makefile from an X11 window and run make from there, but Xcode will also edit the Makefile and I can click Build from Xcode. I was able to build and run the Darwine Xcode template! My PATH setting above was working in the Makefile. It actually was a different error later.
I added the following to Makefile: (Remember I'm on Intel, so you may need to change i386 to your architecture ppc, ppc4, x8664) PATH = $PATH:/Developer/Tools:/usr/libexec/gcc/darwin/i386:/usr/bin There were also warnings about not finding the path /usr/lib/wine I don't know if Darwine (or Darwine SDK) installed this or is missing this library path or if I overwrote it with WineHQ versions, but I (re)installed winehq.com wine-0.9.33 next. WineHQ had minor install problems for me. If./tools/wineinstall doesn't work for you, try from an X11 window (not the standard Mac OS X Terminal window - so you need to have X11 installed)./configure make depend && make make install (this last make requires root or sudo) Then I was able to replace in the Makefile LIBRARYPATH = -L/usr/lib/wine with LIBRARYPATH = -L/mypathto/wine-0.9.33/dlls Don't forget the earlier changes in this thread (Appending to INCLUDEPATH -I/Developer/Headers/Wine/include/wine/windows and CEXTRA and CXXEXTR for i386 or your architecture) I think that's it. Click Build from Xcode.
Succeeded baby! No Warnings and No Errors Then I ran it in an X11 window from /mypathto/wine-0.9.33/ with./wine /mypathto/darwinehelloworld.exe.so Good Luck! Sorry, missed the list. Forwarded message - From: Dee Ayy Date: Mar 25, 2007 1:11 AM Subject: Re: Darwine Xcode can't find windows.h To: Jim White Odd. When I tried a new project, I got 3 warnings. I then commented out my LIBRARYPATH, did a build, expected more warnings/errors and instead it succeeed. I reapplied the LIBRARYPATH, did a build and it still succeeded.
All from Xcode. But I still run from an X11 window. Don't look a gift horse in the mouth? On 3/24/07, Jim White wrote: Dee Ayy wrote: I was able to build and run the Darwine Xcode template! Excellent!
This article needs additional citations for. Unsourced material may be challenged and removed. (April 2017) windows.h is a -specific header file for the and programming languages which contains declarations for all of the functions in the, all the common macros used by Windows programmers, and all the data types used by the various functions and subsystems. It defines a very large number of Windows specific functions that can be used in C. The can be added to a C programming project by including the header file and linking to the appropriate libraries.
To use functions in xxxx., the program must be linked to xxxx.lib (or lib xxxx.dll.a in ). Some headers are not associated with a.dll but with a (e.g. Scrnsave.h needs scrnsave.lib). Contents.
Child header files There are a number of child header files that are automatically included with windows.h. Many of these files cannot simply be included by themselves (they are not self-contained), because of dependencies. Windows.h may include any of the following header files:. excpt.h –. – variable-argument functions (standard C header). windef.h – various macros and types.
winnt.h – various macros and types (for ). basetsd.h – various types. guiddef.h – the type. – character classification (standard C header). – strings and buffers (standard C header).
winbase.h –: kernel services;:kernel services(e.g. CreateProcessAsUser function), access control(e.g. AdjustTokenGroups function).