public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Massimo Balestra <massimobalestra@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Compile perl Win32::OLE module
Date: Sat, 30 Mar 2019 01:43:00 -0000	[thread overview]
Message-ID: <DM6PR11MB3786CFEA78DD3FA64881679CB65B0@DM6PR11MB3786.namprd11.prod.outlook.com> (raw)
In-Reply-To: <76301648869dbc361e8503e8ada2de43@plebeian.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 910 bytes --]


> Hi Massimo.  The following changes should let it compile.  The tests
> working depends on the peculiarities of your Windows version and Excel
> version.  I would, though, highly recommend using ActiveState Perl
> along with their prebuilt module for any OLE work.
>
Thank you Chris for answering.

But the problem is not during the test, but during the compilation
itself (make).

Yes, I know I could use ActiveState, but I don't want to have two perl
installed on my pc. For me it is more important to have cygwin and if
OLE does not work it is less important.

But I would like to have it work, also because it should work.

Thank you again

Massimo


\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-03-30  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 19:56 Massimo Balestra
2019-03-29 22:21 ` Chris Wagner
2019-03-30  1:43   ` Massimo Balestra [this message]
2019-03-30  1:51     ` Chris Wagner
2019-03-30  8:11   ` Achim Gratz

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=DM6PR11MB3786CFEA78DD3FA64881679CB65B0@DM6PR11MB3786.namprd11.prod.outlook.com \
    --to=massimobalestra@hotmail.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).