Re: [Nano-devel] 2.5.1 little fry

[Richard Kolb II]

Wouldn't it have made much more sense, and progress, to say something like:

"Hey guys, I'm trying to build under windows but I'm not having any luck, can anyone point me to what I need to do?"

The readme on the windows zip of nano says how to compile pdcurses, did you follow that?

Rich

Richard Kolb II

On Thu, Jan 21, 2016 at 8:45 AM, frank <address@hidden> wrote:

On 20/01/2016 16:34, Chris Allegretta wrote:

I think the best part of this troll is that the email is flagged as
Spam on my system.

Let me try again, hope never dies.

* I have installed cygwin64 under Windows 7 Professional about 3 weeks ago. After which I have been installing cygwin packages galore: compilers and everything required for compilation.

* pdcurses is not offered by cygwin but can be downloaded and installed in cygwin. Done. I had even to compile it beforehand. You see, the library pdcurses.a is not available for download as the nano's README in the Windows zip package suggests. Neither mentioned in the README is the fact that pdcurses compiles to pdcurses.a even if you compile it with wide-characters and UTF-8. You have to decide whether the symlink of the README example should be e.g. libcurses.a or libncursesw.a.

* The nano's configure script does accept pdcurses. Problems are elsewhere.

* You try then to compile nano for Windows, hours and hours, failure and failure. Why?

* All we know is that the nano code does not show one single instance of _WIN32. Strange. Especially since the project nano-win at github has plenty of #ifdef _WIN32 or #ifndef _WIN32. And especially when you consider that the code related to filesystems but not to NTFS, e.g. types.h and pwd.h, doesn't apply to Windows.

* Normally you compile with './configure' and 'make'. That's exactly what the README tells you. It doesn't tell you that additional scripts are indispensable, it doesn't give the slightest hint what those scripts do. How can the README suggest such an approach while the maintainer himself needs a stack of scripts?

* At this point in time the only way to understand it would be to assume that the scripts in questions do modify the nano source on the fly. The maintainer denies it. What gives? The issue is that nano 2.5.1. for Windows does not compile for mere mortals.

* As things look now the nano maintainer is indeed playing games with the GPL license. And digressing in his reply.

_______________________________________________
Nano-devel mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/nano-devel