From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id SAA22995 for caml-redistribution@pauillac.inria.fr; Wed, 23 Feb 2000 18:47:16 +0100 (MET) Resent-Message-Id: <200002231747.SAA22995@pauillac.inria.fr> Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id TAA19936 for ; Tue, 22 Feb 2000 19:19:32 +0100 (MET) Received: from saul.cis.upenn.edu (SAUL.CIS.UPENN.EDU [158.130.12.4]) by nez-perce.inria.fr (8.8.7/8.8.7) with ESMTP id TAA19893 for ; Tue, 22 Feb 2000 19:19:31 +0100 (MET) Received: from localhost (localhost [127.0.0.1]) by saul.cis.upenn.edu (8.8.5/8.8.5) with SMTP id NAA12081; Tue, 22 Feb 2000 13:15:39 -0500 (EST) To: skaller cc: ohl@hep.tu-darmstadt.de, caml-list@inria.fr Date: Tue, 22 Feb 2000 13:15:39 EST Message-ID: <12079.951243339@saul.cis.upenn.edu> From: "Benjamin C. Pierce" Resent-From: weis@pauillac.inria.fr Resent-Date: Wed, 23 Feb 2000 18:47:16 +0100 Resent-To: caml-redistribution@pauillac.inria.fr Answering my own question... I've been told that statically linking Tk applications is not possible. If you can tell me how to do it (ideally on both Unix and Windows) I'd be delighted to know: this is one of our biggest problems with distributing Unison at the moment. >>From talking to some more experts, the situation appears to be this: Tk can be statically linked, but this doesn't help with portability because when it starts the first thing it does is reads some Tcl scripts. So in any case you can't distribute a complete all-in-one executable: users will have to install (the right version of) Tk to run your program. B