To Do A.11 - Integrate API status into WineHQ
Jeremy Newman
jnewman at codeweavers.com
Wed Mar 24 17:42:40 CST 2004
Ok, I have commited a version of hatky's work. It is in one php file
instead of split across multiple files.
The file is in the tools cvs
http://cvs.winehq.org/cvsweb/tools/winapi_stats.php
I ran it once and the output will be here:
http://www.winehq.org/site/winapi_stats
It will be updated when Alexander runs the wine_release script.
There is one bug we noticed, and I'll leave that for someone else to
fix. The dll name is only showing the first 5 characters. I double
checked, it is getting inserted into the db correctly, so it is
happening sometime after the insert.
Thanks hatky for your work.
On Wed, 2004-03-24 at 14:53, hatky wrote:
> >I'd rather there wasn't a DB. I know it saved time
> >and effort coding
> >wise to do it this way. Future changes will require
> >updates to the db,
> >and that can't be automated the way the current
> >scripts are.
>
> option2
> crontab this:
> mysql -u user -D winapi -H >winapi_stats.html <
> test.sql
>
> now test.sql is a file that can be changed and the
> user is the only thing hardcoded in the crontab....
--
Jeremy Newman <jnewman at codeweavers.com>
CodeWeavers, Inc.
More information about the wine-devel
mailing list