April 2004 - Wine-devel - list.winehq.org

Re: Replace winedefault.reg with wine.inf in README, README.it and PACKAGING
by Lionel Ulmer 20 Apr '04

20 Apr '04

On Tue, Apr 20, 2004 at 09:14:28PM +0200, Ivan Leo Murray-Smith wrote: > As in subject. > License: LGPL * An initial set of registry entries. The current Wine standard is to use the regedit tool against - the 'winedefault.reg' file to generate a default registry. + the 'wine.ing' file to generate a default registry. The current preferred method of configuring/installing It's not 'use the regedit tool against...' but the 'rundll32 tool'. Lionel -- Lionel Ulmer - http://www.bbrox.org/

1 0

DateTimeCtrl doesn't select a new date
by Felipe W Damasio (Elipse Software) 20 Apr '04

20 Apr '04

Greetings, Whe using CDateTimeCtrl and selecting a new date on that calendar thing, the date isn't selected and the widnow isn't closed. In fact, there's no way I can close that window, except closing the program. Attached is a little app Cesar Mello <cesar(a)elipse.com.br> wrote to show this problem. Also attached is the Windows' binary for testing purposes. Tested with the latest wine. Please let me know if I can provide any more info to help this fixed. Thanks in advance, Felipe

3 4

Re: wine/programs/winetest main.c Makefile.in
by Ferenc Wagner 20 Apr '04

20 Apr '04

Alexandre Julliard <julliard(a)winehq.org> writes: > ChangeSet ID: 12069 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2004/04/19 23:00:07 > > Log message: > Ferenc Wagner <wferi(a)afavant.elte.hu> > - Change to console mode so that winetest runs under WinRash. > - Move from spawnvp() to CreateProcess(). > - Force a 2-minute timeout on individual tests. > > Patch: http://cvs.winehq.org/patch.py?id=12069 Hi Alexandre, Is there a forcing reason to have oldstdout initialized to -1 besides playing safe? Not that I object it, just want to avoid grave errors in the future. -- Feri.

2 1

winetest: what next?
by Dimitrie O. Paun 20 Apr '04

20 Apr '04

OK, So assume we get the show rolling, tests will run on various boxes, results will be send back to WineHQ, nice colorful pages will be generated, and a beautiful index page will put all these together, being linked from the Status (http://www.winehq.org/site/status) page. Are we done? I think not. This is a very important piece of infrastructure, and it's buried rather deep into the bowels of WineHQ. Moreover, it's not easy to monitor the changes in testing status. As such, I would like to have a "Weekly testing update" posted to in the News section, with stuff like: how many tests were added, how many failed/successed, etc. since last week. Maybe a list of DLLs where changes were observed, and so on. To get these statistics (and possibly other interesing bits) in the future, I'm thinking at storing all these test results in the database. NB: I'm not proposing that we change the current processing of dissect & gather, it is very nice, and it's a big bonus that it works without a database. All I'm saying is that we can augment dissect to also save stuff to the database. For the database, we need two simple tables: wine_test_releases, and wine_test_results. wine_test_releases: build_id VARCHAR(20) NOT NULL cvs_ts VARCHAR(20) cvs_tag VARCHAR(20) url VARCHAR(256) NOT NULL publish_ts TIMESTAMP NOT NULL This table will be populated by Brian's script, when a new release is publised. One of cvs_ts or cvs_tag will be NOT NULL, and will specify how to get to the exact source used for the build. Nightly builds will use cvs_ts (cvs -D <cvs_ts>), while official releases done by Alexander will use cvs_tag (cvs -r <cvs_tag>). Additional metadata may be required here, suggestions welcome. wine_test_results: build_id VARCHAR(20) NOT NULL tester_id VARCHAR(20) test_name VARCHAR(20) NOT NULL subtest_name VARCHAR(40) NOT NULL file_name VARCHAR(128) NOT NULL line_number INTEGER NOT NULL result INTEGER // 0 = success, 1 = timeout, etc windows_version VARCHAR (15) // 4.3.1233 I've probably missed something, so feel free to add to this. Comments, flames? -- Dimi.

3 3

Winetest results uploaded... where?
by Jakob Eriksson 20 Apr '04

20 Apr '04

winetest.exe from http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ works fine for me in Windows XP, but where is the stuff uploaded? "test.winehq.org", ok fine, but where is the info going? regards, Jakob

2 1

Re: List other downloads on winehq
by Ivan Leo Murray-Smith 20 Apr '04

20 Apr '04

> But since you have not agreed to any license, you are free to personally > use your download however you wish. Thanks to the new EU laws on copyright (Not the patent one, this is another thing), this will soon change. Ivan.

2 1

Appdb - Add submit time to appQueue
by Chris Morgan 20 Apr '04

20 Apr '04

* appsubmit.php, admin/adminAppQueue.php, tables/appdb_tables.sql Chris Morgan <cmorgan(a)alum.wpi.edu> It would be nice to know when entries to the appdb were submitted. Jeremy, you'll want to run this alter command to add the column to the existing table. 'alter table appQueue add column submitTime timestamp;' Comments? Chris

2 1

A Few Newbie questions
by Lonnie Cumberland 20 Apr '04

20 Apr '04

Hello All, I have been watching Wine grow over a period of time and it looks like things are getting better each time that I visit the site. Let me first say "GREAT JOB" to all of the developers on the project. I am wondering a few things and hope someone could take a stab at answering these for me. 1.) Is wine thread save and can I run many instances without problems? Also, can multiple users be running multiple instances without major degrades in system performance for each instance? 2.) What is the main differences between the WineX and Wine developments? Which is more stable? Thanks in advance, Lonnie.

3 2

Wine Directory Mapping sub-system
by Lonnie Cumberland 20 Apr '04

20 Apr '04

Hello All, Is there some where that I can read docs that talk about the directory mapping sub-system? In particular, I am interested in the way that you can "map" user directories in the configuration file in a users HOME directory. What I am thinking about is how one might use this same idea to "Jail" Linux user directories so that users cannot navigate out of their home directory as a security feature. Just playing with ideas, but I thought that the Wine sub-system might offer a great feature for this in that applications could not do anything even if they were to "Break" Out" as they would be going through a translation layer just like the Window applications but onlu still being Linux applications. Any ideas on this? Thanks, Lonnie

2 1

Re: Cross compile fix
by Alexandre Julliard 20 Apr '04

20 Apr '04

Hans Leidekker <hans(a)it.vu.nl> writes: > -.res.res.cross.o: > +.rc.res.cross.o: > $(CROSSWINDRES) -i $< -o $@ Why do you need that? windres should work just fine with a .res file as input. What error do you get? -- Alexandre Julliard julliard(a)winehq.org

3 4