| Re: [AD] Patch: improved website stylesheet |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Mon, Apr 28, 2014 at 12:38 PM, Trent Gamblin <trent@xxxxxxxxxx> wrote:
> On Mon, April 28, 2014 4:29 am, Elias Pschernig wrote:
>> About Windows dependencies, it seems msys2 has a package manager which
>> has binaries for all dependencies (as well as allegro itself):
>> https://github.com/Alexpux/MINGW-packages
>>
>> So at least when using mingw64 to compile, this should make a Windows
>> build extra easy.
>
> Do things in order. Get CMake able to build proper binaries before setting
> up VMs and compilers. 64 bit binaries aren't as important as 32 bit. I'm
> just looking at this horrible non-existant game plan here and cringing.
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?