Ulf,
The problem is that (e.g.) MacOS or OpenBSD
share some code from generic_unix and generic_bsd but has some unique
code as well.
We have to keep this logic somewhere.
We have at least three options:
1. #ifdef -
pro we can slowly migrate from
#ifdef OpenBSD to #ifdef HAVE_MAD_LINKER
cons it pollutes code and doesn't cover all cases.
2. Dir structure
unix/generic
bsd/generic
/OpenBSD
etc
pro - well understandable
cons - still not cover all cases
3. configure that create a build set by overwriting
generic files with platform specific ones when
necessary
pro - could solve whole bunch of problems,
not only platform one.
cons - require some efforts to maintain.
-Dmitry
On 2011-12-01 18:27, Ulf Zibis wrote:
> Am 30.11.2011 23:32, schrieb David Holmes:
>> On 30/11/2011 11:15 PM, Ulf Zibis wrote:
>>> I more would like src/posix + src/winapi
>>>
>>>
>>> Combining Flat vs Hierarchical advantages:
>>>
>>> src/common or 'general' or 'independent' in homage to
>>> platform-independent
>>> src/posix
>>> src/posix.BSD
>>> src/posix.GNU
>>> src/posix.GNU.Linux
>>> src/posix.SYSV
>>> src/posix.SYSV.AIX
>>> src/posix.SYSV.Sun
>>> src/posix.X11
>>> src/winapi
>>> src/winapi.32
>>> src/winapi.CE
>>
>> But the BSD, GNU, SYSV api's are not POSIX - that's the whole point
>
> Oops, sorry for my low knowledge on that. Please only refer it as
> example for a folder naming schema.
>
> -Ulf
>
--
Dmitry Samersoff
Java Hotspot development team, SPB04
* There will come soft rains ...
