Dear Sourceforge;
We need a "Mac guy". Our engine compiles and runs on (old) macs, but we cannot afford new macs. Currently our engine will run for abit and then hits into the newer security features. We can't keep up with the changes and need someone who will make the macros in
common.c
common.h
To make things happy for Mac.
Someone... who has a mac and knows the platform.
It changes so fast for us.
Currently there are macros to deal with linux vs bsd vs windows etc.
Mac is "counted" as one of the BSDs mostly (except in the make file area where it has it's own macros)
For instance: linux is supplied by the code in common.c with the engine's version of strlcpy, since linux doesn't have it. Mac and the BSDs are not.
Explanation:
However today Mac requires memory not overlap, and in the engine, for speed consideration, sometimes it is not checked if a memory location allready has the-same-data that the engine wants to place (ie: it's rewriging exactly ABC where in memory there allready is ABC): this was and is needed on old platforms not to waste compute time on a check. Today platforms are faster: so a macro to supply Mac with a version of strlcpy in common.c that does a check first would be ok for new fast macs. We don't have expertise with this however and wouldn't really know if it works on newer macs so need a "Mac Guy". (Ex: size_t str_l_cpy_for_mac_mx (char dst, const char src, size_t siz) { .....
We know we'll never beable to get our mac bins signed ofcourse, but to have them run and not be ended by the mac security stuff would be nice. And that's just speaking of the memcpy stuff :P
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dear Sourceforge;
We need a "Mac guy". Our engine compiles and runs on (old) macs, but we cannot afford new macs. Currently our engine will run for abit and then hits into the newer security features. We can't keep up with the changes and need someone who will make the macros in
common.c
common.h
To make things happy for Mac.
Someone... who has a mac and knows the platform.
It changes so fast for us.
Currently there are macros to deal with linux vs bsd vs windows etc.
Mac is "counted" as one of the BSDs mostly (except in the make file area where it has it's own macros)
For instance: linux is supplied by the code in common.c with the engine's version of strlcpy, since linux doesn't have it. Mac and the BSDs are not.
Explanation:
We know we'll never beable to get our mac bins signed ofcourse, but to have them run and not be ended by the mac security stuff would be nice. And that's just speaking of the memcpy stuff :P