public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mario Emmenlauer <mario@emmenlauer.de>
To: cygwin@cygwin.com, Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: Could rm remove files and folders with colon in their name?
Date: Wed, 10 Nov 2021 21:23:08 +0100	[thread overview]
Message-ID: <8c027e0b-de0e-bc27-9f69-296c0dc2b0bb@emmenlauer.de> (raw)
In-Reply-To: <67833988-507b-2882-d035-83724bfd2ee6@SystematicSw.ab.ca>


Hi Brian,

On 10.11.21 17:35, Brian Inglis wrote:
> On 2021-11-10 02:45, Mario Emmenlauer wrote:
>> PS: These folders are created when I use the Cygwin-based build system
>> for ICU (see https://unicode-org.github.io/icu/userguide/icu4c/build.html#how-to-build-and-install-on-windows-with-cygwin)
>> For me this is in a combination with native Perl for Windows (ActivePerl,
>> in my case), and using absolute build paths. After using ICU's build
>> system, I can not remove the build tree anymore. It may be possible to
>> solve this on the ICU side too. But their automake-and-Perl-based path
>> mangling is not easily modified, and I've failed to isolate the root
>> cause of the illegal paths.
> 
> Install the Cygwin cygport and libicu-devel source and binary packages and use only Cygwin exclusively with cygport to avoid problems.


I'm not sure that this is what I want. I want to build ICU with Visual
Studio and the ClangCl compiler frontend from LLVM 13.0.0. Their build
system can use Cygwin for this combination to orchestrate and configure
the build - which I very much like :-)

Sorry that I did not mention this in my email.

The build works fine and I get native ICU shared libraries like I want.
The only "downside" is that it creates the unsupported folders :-)

Cheers,

    Mario


--
BioDataAnalysis GmbH, Mario Emmenlauer      Tel. Buero: +49-89-74677203
Balanstr. 43                   mailto: memmenlauer * biodataanalysis.de
D-81669 München                          http://www.biodataanalysis.de/

      reply	other threads:[~2021-11-10 20:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  9:45 Mario Emmenlauer
2021-11-10 13:49 ` Corinna Vinschen
2021-11-10 20:24   ` Mario Emmenlauer
2021-11-10 20:39     ` Corinna Vinschen
2021-11-11 14:00       ` Mario Emmenlauer
2021-11-24 15:40       ` Chris Wagner
2021-11-10 14:49 ` Andrey Repin
2021-11-10 16:35 ` Brian Inglis
2021-11-10 20:23   ` Mario Emmenlauer [this message]

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=8c027e0b-de0e-bc27-9f69-296c0dc2b0bb@emmenlauer.de \
    --to=mario@emmenlauer.de \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --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).