On Fri, 3 Mar, 2017 at 3:19 PM, Adrien Destugues <pulkomandy@xxxxxxxxxxxxx>
wrote:
Hi, welcome to Haiku! First, if you have already contributed something to Haiku
or HaikuPorts, please include links to it (here or in your proposals). Even if
it is not directly related to your project proposal, existing contributions are
nice to have.
Hi Adrien!,
Here are the list of contributions I have made under HaikuPorts so far:
https://github.com/haikuports/haikuports/pulls?q=is%3Apr+author%3Areturn+is%3Aclosed
If you want to contribute something related to the project, for the first idea,
you could look into Haiku bugs for Tracker. Or, you could also study existing
software (MoleSVN, PonpokoDiff, etc) that may be related (there was a thread
listing some of those in Haiku forums quite recently). Regarding the second
idea, it looks like getting Swift somewhat running was not too hard for
FreeBSD. However, it may not be as easy for Haiku. While we have all the
dependencies, some of them may be incomplete or not working as expected. I
would expect some problems in Python3 and in LLVM. You will probably see what
kind of problems you get if you try to build Swift. I think solving some of
these issues would make for nice patches, showing you know where you are going
with the project.
Also, don't hesitate to join the haiku-development mailing list if you want to
get into more technical discussions.
--
Adrien.
I have another question, whilst building some of Haiku's user-space
applications, how do I get Jam to generate debugging information so it can be
used by 'Debugger'? Whenever I start a debugging session, I just see the
assembler output by default.
Thanks,
Joseph, C Hill