Yeah I have the jamfiles configured (though it is a copy of what you did in
your repo, just the names changed here and there). I can build drm using
"jam -qj4 drm" though I have all the files commented out right now.
Here's the drm jamfile
<https://github.com/vivek-roy/haiku/blob/3aa8c135fdfbe3e76347dea5767f82a7d0b1d86b/src/add-ons/kernel/drivers/graphics/drm/Jamfile>
On Thu, Jun 8, 2017 at 2:37 AM, Hamish Morrison <hamishm53@xxxxxxxxx> wrote:
On 07/06/2017 21:37, Vivek Roy wrote:
Of course a lot of things will need porting - but don't just assume
everything does because it includes some random header files :)
Having a hard time figuring that out.
What is the best way to test if a header file works or not? I mean, I
removed all the includes from list.h, I want to check if it works. (What
comes to my mind is making a test cpp file where I include list.h,
anything better than that?)
Yeah writing unit tests for the files you port is always a good idea
(although if they're taken verbatim from FreeBSD this might be overkill).
To simply check that it builds you can import it into the source tree and
build the Linux KPI with Jam. Have you set up a development environment for
building the Haiku source?
