Re: [AD] Don't use Devpaks |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
>Dev-Cpp is actually just an IDE, it sometimes comes bundled with Mingw32
>(which is a compiler), but its pretty ancient now. Whoever maintains the
>devpak could talk about it more, but i can't remember who that is, I don't
>believe it's officially supported, unlike the MSVC, and MSYS packages. I had
>thought there was a generic Mingw package too, not 100% certain about that
>mind you.
Yeah, you can use it with many other compilers, but I like the default one
because it is the only one I know that allows it to be portable. Dev-Cpp
allows you to import MSVC projects (not sure how well it works for that yet)
and there are some branches of Dev-Cpp that sound interesting, like the
wxDev-Cpp with the built-in GUI designer.
>> Using MSYS2 to install a Linux environment in Windows so you can use a
Linux
>> compiler is a joke. This needs to be done right and using Dev-Cpp was the
>> right way to do it. If your best advice is "you are on your own", then
>> Allegro is a dead project or it needs to be.
>Allegro 4 is pretty much dead now. Allegro 5 though is not, and has working
>packages for MSVC, MSYS, and MingW iirc.
I suppose all I want to know for a fact is, are the Allegro 5 APIs written in
C++ or C?