Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199905061633.LAA02457@modi.xraylith.wisc.edu> X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol To: Juergen Koehne cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Problem running a C/C++ program evaluating a tcl script In-reply-to: Your message of "Thu, 06 May 1999 17:31:19 +0200." <3731B5C5 DOT 57BF7276 AT ulm DOT temic-semi DOT de> Date: Thu, 06 May 1999 11:33:40 -0500 From: Mumit Khan Juergen Koehne writes: > > I've troubles running a C/C++ program evaluating a Tcl script. The > program compiles without errors, but when I run it only the Tcl prompt > appears on the command line but no window pops up. > Under Unix and Linux all works well. When I start the program the popup > window appears as expected. > Has anyone an idea what's going wrong? > Short and pat answer -- you're doing it correctly ;-) This has come up in the past and answer hasn't changed -- Unix and Cygwin ports of Tcl are not the same (unless you build Cygwin Tcl as a Unix one, which is not the case in the Cygwin distribution)! Two choices: - For truly portable Tcl code, you should use dynamic loading, and nothing but dynamic loading. It's simple and it works. - If you really must have a "main" function and create all the interpreters yourself as you're doing, then you need different "main" programs for Unix and Windows32. Tcl folks have some examples to show how this is done, and you should look at the example.zip or example.tar.gz somewhere on Scriptics site. Also, check the FAQ, which might have some more pertinent information. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com