you're supposed to run fixdll from the allegro basedir ie: misc/fixdll.bat

and the fixdll scripts need a few unix like tools, like sed and sort. Make sure they are in the PATH or the script cant find them.

How are you changing your PATH? From the windows dialog for it? Or just using "Set" in the cmd?

If you change it from the dialog, you're going to have to close your cmd window and re open it to see the changes (some people say log out and back in, but I think re opening the cmd window is all that is really necessary). If you're changing PATH directly in th current cmd window, it should work as is (but you have to keep changing it every time you open a new cmd window).

As I mentioned previously, you're supposed to run it from allegro's base dir, not from inside misc. ie:

mics/fixdll

You're still running it from inside misc, cd up to "svn allegro 5" and retry.

Also, I'd suggest strongly that you not put allegro or mingw in folders with spaces in them.

Probably worth mentioning in this thread...

MinGW doesn't have gcc.exe, but gcc-3.exe. It has a shortcut called gcc, but it somehow doesn't get invoked. I had to modify the batch file to get it to work.

Also, Windows will choke if you don't already have the lib* directories made.

It's probably a good idea to get MSYS and invoke fixdll.sh instead of fixdll.bat.

Then this behaviour will be no problem...

...and I don't know what else is different.

It was an advice of one of the allegro devs. Thats why I'm doing it this way.
If the creation of the dir is all that changes, then you are right, then it's an overkill.
But I don't know if the sh file is doing other things in a different way as well, thats why I sticked with the advised way.
Will compare the two files later to check what the diffrences actually are.
Or if you already did and the dir creation is the only diffrence then it would be ok too.

You can always build a static version and not care about the def file.

Hey guys,

Thanks for the response ... I had to travel to the in laws, but no worries the comp is with! (gotta love VHS to DVD weekends)

Thomas-
Thx for putting up with me at midnight. As you could tell late night + programming doesnt mix. I did run the fixdll up in the "root" folder.

1)Then I had issues with the output folders, as Kibiz0r pointed out, so I created them and re-ran fix dll. To my surprise it worked.

Then I had the dll , which I have left in place in the lib\mingw32 folder.

(LennyLen- Thx for the upload but I didn't use it)

2)As far as my MinGW version I don't know since I was lazy and used the installer, but I did dredge up this from the install.ini:

3)I MAY use MSYS eventually, but who knows.

4) Now I tried to Cmake like I normally do, but I had 3 errors come up:
-libjpeg not found
-libFLAC not found
-libsndfile not found

THEN I found the forum with the dependancy files, and once those were installed I no longer had any configuration issues.

YET, I'm not in the clear. I attempted to build the file (via Code::Blocks), and I have errors with the joystick:

I will be forum crawling and rechecking my steps to see if I can pin the problem.

Thx again all ^_^

Eh?
What does that mean? I assume it's some sort of dialect?

Trent-
I did grab those files the other day, but re-downloaded/replaced the files for kicks and now I'm getting this:

Yah it's North Dakotan ... sorry about that. (I need to get out of the state my Minnesotan is disappearing everyday)

EDIT 5:43

So I tried for kicks to have a new check out folder and build everything off of that and now the issues are with the d3de9x files/config etc :

Does anyone know what would happen if I left it disabled in the cmake options? ...since I am running vista?

My knowledge is vague as best. Is it supposed to be an opengl replacement? Or can I still use opengl?

Also it appears to be building now ~85% done

Update:

Now I just have to play around with the libraries...