lol, you were right.
I also installed a fresh copy of the March SDK and I found it.
I also found a very interesting thing. In the environment variables:
Name: DXSDK_DIR
Value: D:\Program Files\Microsoft DirectX SDK (March 2008)\
And of course I didn't put that there myself.
So I guess I could use that. Please tell me how/what should I modify so MinGW would know where the SDK is. (Also searching myself)
Edit: Didn't found it myself.. Let's try google..
Thanks.
[fixed] Revision 1309 doesn't compile with MinGW - Win32
-
- Posts: 1186
- Joined: Fri Dec 29, 2006 12:04 am
Again: Edit the Makefile.MasterGod wrote:Please tell me how/what should I modify so MinGW would know where the SDK is.
That's one of the weirdest thing I've ever had to deal with.
All I did (after many attempts) was to just copy the Include directory of the DirectX SDK and add the path to that directory in Irrlicht's Makefile and it worked.
I never had to do that , very weird IMO, but it works
Thanks you guys for helping me, it was very important for me to fix this problem, so thanks again!
P.S
What does the 'all_win32' means?
All I did (after many attempts) was to just copy the Include directory of the DirectX SDK and add the path to that directory in Irrlicht's Makefile and it worked.
I never had to do that , very weird IMO, but it works
Thanks you guys for helping me, it was very important for me to fix this problem, so thanks again!
P.S
Code: Select all
mingw32-make NDEBUG=1 all_win32
take a look at the makeFile, it'll tell you a lot about what those commands do
Here's the relevant lines, I believe:
right below it are the lines
which means that you can build Irrlicht as a .dll (that's the all_win32), which calls sharedlib_win32. At least, I think that's what it does... I never was very good with MakeFiles O.o
-wyrmmage
Here's the relevant lines, I believe:
Code: Select all
# Builds Irrlicht as dll (Irrlicht.dll) into ../../bin/Win32-gcc
all_win32 win32: sharedlib_win32
Code: Select all
sharedlib_win32: $(IRRLICHT_DLL)
-wyrmmage
-
- Admin
- Posts: 14143
- Joined: Wed Apr 19, 2006 9:20 pm
- Location: Oldenburg(Oldb), Germany
- Contact:
Why don't you use a project file, there's no need to use a Makefile in your setting. Otherwise you'll have to adjust the Makefile to your local needs.
Copying header files to include paths known to the Makefile is one way, a better way would've been to add the additional path.
The all_win32 means it's the all target for win32 systems. The name was arbitarily chosen, resembling the typical all default (which was already reserved for the linux part of the Makefile). Another possible target is staticlib_win32 (or win32, or sharedlib_win32, but those do the same as all_win32).
Copying header files to include paths known to the Makefile is one way, a better way would've been to add the additional path.
The all_win32 means it's the all target for win32 systems. The name was arbitarily chosen, resembling the typical all default (which was already reserved for the linux part of the Makefile). Another possible target is staticlib_win32 (or win32, or sharedlib_win32, but those do the same as all_win32).