• Samuel (5/5) Dec 07 2020 I was wanting to run some D code on an OpenBSD server. I have
• kinke (8/10) Dec 07 2020 That's one way; make sure to try to link the unittests too
• Jacob Carlborg (8/12) Dec 11 2020 Yes, unfortunately the platform specific code is not located in a single...

Samuel <ssamm1545 gmail.com> writes:

I was wanting to run some D code on an OpenBSD server. I have 
already successfully built LDC 0.17. Does anyone have advice for 
getting started porting druntime? Should I just go through 
druntime/phobos and start adding OpenBSD definitions until it 
compiles successfully?

kinke <noone nowhere.com> writes:

On Monday, 7 December 2020 at 19:49:15 UTC, Samuel wrote:
 Should I just go through druntime/phobos and start adding 
 OpenBSD definitions until it compiles successfully?

That's one way; make sure to try to link the unittests too 
(`ninja druntime-ldc-debug phobos2-ldc-debug 
druntime-test-runner-debug phobos2-test-runner-debug`).

Grepping for `FreeBSD` (which is CI-tested) and adding/verifying 
OpenBSD declarations would be another approach.

Your patches should then be submitted to *upstream* 
druntime/Phobos. Thanks in advance!

Jacob Carlborg <doob me.com> writes:

On 2020-12-07 20:49, Samuel wrote:
 I was wanting to run some D code on an OpenBSD server. I have already 
 successfully built LDC 0.17. Does anyone have advice for getting started 
 porting druntime? Should I just go through druntime/phobos and start 
 adding OpenBSD definitions until it compiles successfully?

Yes, unfortunately the platform specific code is not located in a single 
directory, as one could have hoped for. Both druntime and Phobos will 
have platform specific code scattered all over the place. Most of the 
platform specific code is in druntime. A lot of it will be bindings to C 
APIs.

-- 
/Jacob Carlborg