On 05/17/2010 07:14 AM, Paweł Blokus wrote: > Hi, > > My name is Paul Blokus and during this summer I will be creating unit > tests for drizzle as a GSoC student. I decided that the best way of > determining what should be done first would be asking all the drizzle > developers for their opinion. For this reason I have created the wiki > page at http://drizzle.org/wiki/UnitTests. I encourage you to set the > priorities and write comments so that the most important parts get > their tests first and any pitfalls (like code that's going to be > removed) can be avoided. > > Sorry for initiating this so late but my university duties kept me > from any additional activities :(
Just wanted to give a quick heads up on the status of this project from my end. (build integration) I'm having to do some re-arranging of how things link in the server, because when we write the unit tests (for things that aren't the header-only atomics code) we have to link in the proper symbols for the test to run. PROBLEM IS - what to link with? We aren't a library, after all, and as it stands now building a shared libdrizzled and then linking a shim around it to make drizzled is FAIL (and will be until we can mark default symbol visibility to hiddne) So I've got some revisions in my branch which builds off of the shared libdrizzled branch but does it as a static convenience lib, so that the resulting drizzled binary is the same, but which allows us to link test programs to the server symbols. It's 95% done - there is some weirdness around how dtrace symbols are processed/linked. I should have this in the next day or two, at which point we should be able to merge Paweł and Stewart's branches in. Monty _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
