You install the nuget package, then just use the include files as needed in your source. The nuget package will add a property screen where you select what features you want, how you want it built, and it will handle the lib stuff for you.

It's like that pkg-configure (I think that's the command) on Linux.

{"name":"610435","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/8\/084e43eb6c2f2ef0adfa6bfe1d7eb420.png","w":1307,"h":297,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/0\/8\/084e43eb6c2f2ef0adfa6bfe1d7eb420"}

2015 might have change things a tad, but this is what I was talking about with the property page.

Also, my include is define like this: $(ProjectDir)\include;$(IncludePath)

Then I just use #include <allegro5/allegro.h> (Note, $(ProjectDir)\include is a by product of using the SpeedHack makefile and allowing that to work with my code)

This looks like a great update. Thanks to everybody involved for their hard work.

Are binaries (not a Nuget package) available for MSVC2015? I prefer managing libraries the "traditional" way, but if not the package is usable.

My game is made with Allegro (http://store.steampowered.com/app/363220/), perhaps it will benefit from a new build with the update library (I think it runs on 5.0.9 still).

The allegro.cc files page should probably be updated, too.

I may try one last time. I tried an install where I removed ALL files pertaining to Allegro 5. I'll try re-installing MinGW from scratch along with Allegro from scratch and see how that goes but I have my doubts. My paths are all fine, I done clean installs, clean builds.

If that works, I'll let you know, if not... I just won't bother. I don't work with this enough anymore.

Sorry, it was MY fault. I checked my paths and sure enough, there is another path it checks that had an older Allegro in it. Works fine now, thanks for all your work and help. I didn't mean to be a pain, I just don't work on this as much as I used to, so I am a little rusty at times. I'll recompile the game and put up a new version of it using your latest build.

It correctly reported 5.2.1 etc... on both versions as well. I guess I need to put a note somewhere reminding me where all my folders are to avoid future headaches (and unnecessary reports here).

Thanks again "Edgar"

Edit: My game, now compiled with this version, can be downloaded here (game play video on the page too): http://home.cogeco.ca/~nroy15/games_index.html

@AMCerasoli: You should visit us more often.

Okay, I solved all of my earlier problems.

I have some concerns with debugging my program with MSVS and Allegro with the Nuget package though.

1. Sources aren't included so I can't see what code is causing an exception. For instance, right now it's crashing in al_mutex_lock inside al_register_destructor inside al_create_timer. It looks like al_install_system succeeded though, so I don't know what would make it crash in al_create_timer, and I can't look at the sources because they don't come with the Nuget package.

2. allegro_debug.pdb wasn't copied over into the Debug folder when I installed the Allegro Nuget package, so I had to do it manually to get the symbols for allegro to show up in the debugger.

Here's a screenie of what I mean. You can see the local variable window is empty, so I can't view the value of any of the local variables, like the mutex and it's critical section member. So I can't tell why it's crashing, and I'm stuck. Every time I try to switch to the frame where it is crashing, it says I have to have the source file to view it. Ideas?

{"name":"610451","src":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/f\/a\/fa7eb5321ebe756665d19c4baf57c93b.png","w":1919,"h":847,"tn":"\/\/djungxnpq2nug.cloudfront.net\/image\/cache\/f\/a\/fa7eb5321ebe756665d19c4baf57c93b"}