On 07/31/17 05:24, Stuart Henderson wrote:
> On 2017/07/30 17:33, Brian Callahan wrote:
>> Hi ports --
>>
>> Attached is a new port, games/corsixth. CorsixTH is an open source clone of
>> the game Theme Hospital.
>>
>> ---
>> pkg/DESCR:
>> CorsixTH is a reimplementation of the 1997 Bullfrog business sim Theme
>> Hospital. As well as faithfully recreating the original, CorsixTH adds
>> support for modern operating systems, high resolutions, and much more.
>>
>> CorsixTH requires game assets from Theme Hospital to work properly.
>> ---
>>
>> You will have to obtain a copy of Theme Hospital to play this (the GoG
>> download worked for me using innoextract to extract it, like with OpenRCT2).
>>
>> This requires a C++11 compiler. In theory, CorsixTH should work on any
>> platform even those that don't have clang as their base compiler (I don't
>> have the hardware to test, sadly). I don't think it's appropriate to do
>> ONLY_FOR_ARCHS=${CLANG_ARCHS} unless the theory doesn't work out in
>> practice. What's the best way to do this?
>> COMPILER = clang gcc
>> MODCLANG_ARCHS = <some list that doesn't include ${CLANG_ARCHS}>
>> MODGCC4_ARCHS = <some list that doesn't include ${CLANG_ARCHS} or
>> ${MODCLANG_ARCHS}>
>> Does this make sense?
> Standard way to do this would be "COMPILER = gcc" or "COMPILER = clang gcc",
> and "ONLY_FOR_ARCHS = ${CXX11_ARCHS}".
>
> It seems like it could use a README or something with information about
> how to buy/extract/install the required files?
>
I think a README is a great idea. I'd like to add the same to OpenRCT2
as well since it's in the same position, if that's OK with you.
Attached is a new tarball for everyone. I added the compiler logic and
changed the name of the launcher script to CorsixTH from corsixth since
at least FreeBSD does it that way. Might as well be consistent with others.
OK?
~Brian
No comments:
Post a Comment