[Issue 11666] Separate each platform's port to its own folder/file: aka "if version{} else version {}" getting out of control

[d-bugmail at puremagic.com]

https://d.puremagic.com/issues/show_bug.cgi?id=11666



--- Comment #4 from Martin Nowak <code at dawg.eu> 2013-12-04 11:52:04 PST ---
(In reply to comment #0)
> ** begin quote **
> Personally I feel that people porting to specific architectures should
> maintain their differences in separate files under a /ports directory
> structure - lets say core.stdc.stdio as a cod example. The version for
> bionic would be under /ports/bionic/core/stdc/stdio.d, and that is the
> module that gets compiled into the library when building for bionic.
> When installing, the build process generates a header file of the
> bionic version of core.stdc.stdio and puts the file in the correct
> /include/core/stdc/stdio.di location.

That sounds almost like a feasible approach. Can you go into more detail
though.
Would we create a complete copy of druntime under the ports tree or just for
the files'that differ.
What about the combinatorical explosion of libcs x archs, i.e.
/ports/bionic_arm, /ports/bionic_x86 and /ports/glibc_ppc? Porting the bits
folders for glibc would be the straightforward solution IMO, don't know about
other C libs.
How does this integrate with our core.sys.posix and core.sys.linux layers?

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------