public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Windows Subsystem For Linux
Date: Tue, 30 Aug 2016 17:45:00 -0000	[thread overview]
Message-ID: <9eee718d-1fb9-3091-48f2-bc7764d88f4d@gmail.com> (raw)
In-Reply-To: <1454779106.2980080.1472543049625@mail.yahoo.com>

On 30/08/2016 09:44, lloyd.wood@yahoo.co.uk wrote:
> A viewpoint on this whole Windows Ubuntu Frankenstein hybrid vs Cygwin thing:
>
> In comparison with the difficulties trying to build Geomview under 64-bit Cygwin,
> then discovering the piping issues that prevent it working with modules, using
> the Windows Ubuntu subsystem to install pre-existing Ubuntu packages and dependencies
> turned out to be surprisingly straightforward and user friendly.
>
> Compare the instructions on:
> http://personal.ee.surrey.ac.uk/Personal/L.Wood/software/SaVi/building-under-Windows/
>
> and you can see why the complex build-on-Cygwin instructions are now listed last. (I also had
> no problem pulling in gcc and tk-dev and building SaVi from source. Haven't yet tried with
> Geomview!)
>
> I think Cygwin's Xming will soon be the most popular Cygwin spinoff, filling the same
> free Xserver role that XQuartz does on Mac OS X now that no longer ships an Xserver
> with the OS, and I think we're all going to be very grateful that Xming exists.
> https://en.wikipedia.org/wiki/Xming
>
>
> Lloyd Wood
> http://savi.sf.net/
>

I will not use your experience on geomview / savi as standard reference 
of effort for porting software to cygwin.

Last June I had little problem to built geomview-1.95 from source.
It was almost vanilla effort with minimal patch.

Savi needed a bit more of effort but it was mainly due to the old
style of building method and the peculiar startup script.

I doubt the communication issue between the 2 packages on 64 bit
are really due to "piping issues", I suspect more a wrong assumptions
in the chain and I will not bet on tcl/tk correctness.

My effort and the cyport files are located here:
http://matzeri.altervista.org/x86_64/index.html

feel free to reuse it.

Regards
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-08-30 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1454779106.2980080.1472543049625.ref@mail.yahoo.com>
2016-08-30 13:06 ` lloyd.wood
2016-08-30 17:45   ` Marco Atzeri [this message]
2016-08-30 21:27   ` Andrey Repin
2016-08-31 10:51     ` Erik Soderquist
2016-09-04  7:35       ` Herbert Stocker
2016-08-30 13:40 Schwarz, Konrad
  -- strict thread matches above, loose matches on Subject: below --
2016-08-29 12:42 Schwarz, Konrad
2016-08-29 12:54 ` Ray Donnelly
2016-08-29 13:17   ` Tim Prince
2016-08-29 14:22   ` Keith Christian
2016-08-29 17:43 ` Andrey Repin
2016-08-29 18:30 ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9eee718d-1fb9-3091-48f2-bc7764d88f4d@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).