Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Nov 1999 15:00:02 -0800 (PST)
From:      Juergen Lock <nox@jelal.kn-bremen.de>
To:        freebsd-ports@FreeBSD.org
Subject:   Re: ports/14889: [PATCH] dynamic loading for WINE port
Message-ID:  <199911152300.PAA41775@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/14889; it has been noted by GNATS.

From: Juergen Lock <nox@jelal.kn-bremen.de>
To: sobomax@altavista.net
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: ports/14889: [PATCH] dynamic loading for WINE port
Date: Mon, 15 Nov 1999 23:43:49 +0100 (MET)

 In article <19991115024901.CEEF314C1C@hub.freebsd.org> you write:
 
 >Attached patch enables feature which allows WINE port to build dlls'
 >code in a shared library separately from the main WINE's code. This
 >should (at least teorethically) reduce WINE's memory footpring,
 >especially when several WINEs loaded simulateneously.
 
 Well actually if you're running several instances of the same statically
 linked program its entire text segment will already be shared anyway,
 shared libraries are only needed for the different-programs-using-the-
 same-lib case.  So this will only make a difference if you have
 other programs besides wine itself that are also using libwine, but of
 course to prepare for that it might still be a good idea... (provided
 that it doesn't interfere with debugging, i.e. have you checked
 that wine's debugger works as well with the shared libwine?  As wine
 still is alpha and depends on meaningful bugreports from users this is
 a pretty important point, this is also why the port builds with -g
 and installs un-stripped...)
 
  Btw there already is one such program in the queue (wine's regapi), tho
 that one never runs for longer than a few seconds and usually shouldn't
 be used while a wine process is running anyway (unless you're only
 _reading_ the registry), so for this one it still wouldn't make that
 much of a difference.  (besides saving some diskspace that is.)
 
  Oh and btw be careful with running several instances of wine at the
 same time if for example you do something that changes the registry,
 currently wine doesn't synchronize changes with other instances of
 itself so simply the last one writing the registry wins!  (I hope
 it only writes it back if there were changes, otherwise its the last
 one you quit...)
 >
 >Also fix for a small Makefile inconsistency provided as well (typo: MAN1
 >instead of MAN5).
 
  Oh, thanx! :)
 
  Regards,
 -- 
 Juergen Lock <nox.foo@jelal.kn-bremen.de>
 (remove dot foo from address to reply)
 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911152300.PAA41775>