On 15/03/18 01:38, Kieran Duggan wrote:
Hello, I am a computer science student at the City College of New York. I have used Linux for a few years now and have frequently relied on Wine to run windows applications, so the opportunity to contribute to Wine is exciting to me.
I have successfully built wine from source and ran Ski Free on it to test if it worked. Next I wanted to try and find some of the fixmes that were popping up so I could attempt my first patch, however I am having trouble finding where exactly in the source the fixme's are arising. Maybe It's obvious and I'm just too tired right now to figure it out, but I would be very appreciative if someone could point me in the right direction with this.
While I have been learning computer science for years now, I have not yet contributed to an open source project. I am very eager to learn and become familiar with the process.
Thank you! Kieran Duggan
Hello Kieran, and thanks for your interest in Wine and GSoC!
A fixme: message prints out the name of its component, then the function in question, and then some further information. For example:
0041:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
is printed in the NtLockFile() function, which is part of ntdll. It's printed in the source by a FIXME macro:
dlls/ntdll/file.c:3424: FIXME("I/O completion on lock not implemented yet\n");
In general you can just grep for the function name. I hope this helps.
Also please feel free to ask about any specific FIXME or bug before trying to tackle it. A fair number of features are as yet unimplemented because they're more work than they're worth.
ἔρρωσο, Zeb