Re: [AD] Patch: improved website stylesheet |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Mon, April 28, 2014 4:59 am, Elias Pschernig wrote:
> mingw64 is a compiler for 32 as well as 64 bit, the old mingw32 (which
> is 32-bit only) just isn't really developed much right now. Also,
> 32-bit binaries are limited to around 2GB of RAM. But again, the
> reason for mingw64 is just that it's the most maintained fork right
> now.
>
> And I agree, we unfortunately will need some cmake improvements along
> the way. But the current build mostly is able to build binaries - so I
> think we are in fact ready to setup VMs and so on. Which specific
> feature of CMake we need for "proper binaries" are you referring to?
I think the biggest issue is library naming and static/dynamic libraries.
Allegro library naming should be fine as it is, but on Windows library
names can vary depending where you get them from. IMO the best thing to do
is use the latest source archives of each dependency and use the default
names those give to the libraries. Sometimes static/dynamic have different
names so account for that. For things we can't distribute, document what
you need to do. For example you should build with the latest DirectX SDK.
You'll need the platform SDK installed for MinGW and for audio you need to
copy a few headers (sal.h and 1-2 related.)