public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* Re: cygwin Digest 17 Jun 2017 08:20:29 -0000 Issue 10294
       [not found] <1497687629.111995.ezmlm@cygwin.com>
@ 2017-06-17 18:20 ` Stephen Lyons
  2017-06-24  8:23   ` Csaba Raduly
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Lyons @ 2017-06-17 18:20 UTC (permalink / raw)
  To: cygwin


[-- Attachment #1.1: Type: text/plain, Size: 2380 bytes --]

I am new to *writing* to mailing lists so if I've done something wrong
please forgive me.

I would like to "cygport" the Mudlet GPL MUD {Multi-User Dungeon} client
to Cygwin - I have a cygport file (and currently a patch) that works to
compile a workable binary of the 3.1.0 release available as a tarball
from https://github.com/Mudlet/Mudlet/archive/Mudlet-3.1.0.tar.gz {other
distribution methods are available!} but Mudlet possesses a Lua
sub-system that users/MUD system operators can use to provide additional
functionality and this is currently proving awkward!

The issue I am having is that Mudlet needs some Lua "modules" to operate
and Cygwin currently only provides a sub-set of the needed ones, the
lua-file-system "lfs" IS available but also needed is:

* "rex_pcre"

* "zip"

* "luasql.sqlite3"

What is the best way to get those "run-time" dependencies into Cygwin? I
have found "luarocks" packaged versions (as "lrexlib-pcre", "luazip" and
"luasql-sqlite3" respectly) but it is not immediately apparent how I
might use that to generate the things needed as part of the "cygport"
process.

For the record Mudlet {https://www.mudlet.org} is carried on, at least,
the Debian & Ubuntu GNU/Linux distributions and it's developers do
target and aim to provide Linux, macOs and Window platform binaries as
well as source code. However the Windows one does suffer a little in
bug-fixes and performance because it is difficult to put together a
development platform (IMHO) for that OS that will work in both a 32 and
a 64 bit environment (as until very recently) the Qt people only made a
32 bit FOSS development environment available with a built-in Mingw
compiler and, of course, the alternative free MSVC compiler can not be
used to make binaries that can be distributed under GPL terms; the need
to compile/source the other libraries that Mudlet uses in a form that is
compatible with anything compiled with such a Qt/Mingw combination makes
the Cygwin environment much more user friendly for normally *nix system
based developers...

I should perhaps point out that I *am* one of the "upstream" i.e. a
member of the team that call ourselves the "Mudlet-makers" and I have
been using Cygwin on and off for years now... 8-)

I do miss the Qt Creator IDE when I switch to the Cygwin environment
though. 8-(

Stephen



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 538 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: cygwin Digest 17 Jun 2017 08:20:29 -0000 Issue 10294
  2017-06-17 18:20 ` cygwin Digest 17 Jun 2017 08:20:29 -0000 Issue 10294 Stephen Lyons
@ 2017-06-24  8:23   ` Csaba Raduly
  0 siblings, 0 replies; 2+ messages in thread
From: Csaba Raduly @ 2017-06-24  8:23 UTC (permalink / raw)
  To: cygwin list

On Sat, Jun 17, 2017 at 8:20 PM, Stephen Lyons  wrote:
> I am new to *writing* to mailing lists so if I've done something wrong
> please forgive me.
>
> I would like to "cygport" the Mudlet GPL MUD {Multi-User Dungeon} client
> to Cygwin - I have a cygport file (and currently a patch) that works to
> compile a workable binary of the 3.1.0 release available as a tarball
> from https://github.com/Mudlet/Mudlet/archive/Mudlet-3.1.0.tar.gz {other
> distribution methods are available!} but Mudlet possesses a Lua
> sub-system that users/MUD system operators can use to provide additional
> functionality and this is currently proving awkward!
>
> The issue I am having is that Mudlet needs some Lua "modules" to operate
> and Cygwin currently only provides a sub-set of the needed ones, the
> lua-file-system "lfs" IS available but also needed is:
>
> * "rex_pcre"
>
> * "zip"
>
> * "luasql.sqlite3"
>
> What is the best way to get those "run-time" dependencies into Cygwin? I
> have found "luarocks" packaged versions (as "lrexlib-pcre", "luazip" and
> "luasql-sqlite3" respectly) but it is not immediately apparent how I
> might use that to generate the things needed as part of the "cygport"
> process.

I imagine luarocks may work similar to Perl's CPAN on Cygwin: some
Perl modules can be installed via Cygwin's setup.exe (e.g. perl-Tk,
perl-Data-Dump), the rest can be installed with the CPAN client.

IANALU (I am not a Lua user), but it seems to me that these Lua
modules should be outside the scope of Mudlet's cygport. Mudlet should
simply require these modules to be present for its Lua subsystem. The
user can be directed to install the required modules by whichever
means available (rex_pcre and luasql.sqlite may be too complicated to
be installed by luarocks; they may need to be made into Cygwin
packages like lua-file-system).

Mudlet should not mess with the user's Lua installation.

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

--
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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-06-24  8:23 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1497687629.111995.ezmlm@cygwin.com>
2017-06-17 18:20 ` cygwin Digest 17 Jun 2017 08:20:29 -0000 Issue 10294 Stephen Lyons
2017-06-24  8:23   ` Csaba Raduly

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).