public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Carlo B." <carlo.bramini@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygport: CYGCMAKE_SOURCE seems to have no effect.
Date: Fri, 17 Sep 2021 10:18:04 +0200	[thread overview]
Message-ID: <CADt9574_sW83-RWjj2-gzzqt6WKMqDQM6+UdqB6F1gZRejGC5Q@mail.gmail.com> (raw)
In-Reply-To: <486d92a2-6d5c-3fda-f163-c710939b7e23@SystematicSw.ab.ca>

Hello,

thank you for your message,

> Worked just fine for a recent update of fortune-mod.
>
I gave a look to the source tree inside the package
fortune-mod-3.6.1-1-src.tar.xz and the CMakeLists.txt is into the
top-level directory, so it is not the same thing. And it seems to me
that ${CYGCMAKE_SOURCE} is not used by fortune-mod.cygport.

> See online or under your Cygwin directory:
>
>         https://cygwin.github.io/cygport/cmake_cygclass.html#robo765
>
>         cygstart /usr/share/doc/cygport/html/manual/cmake_cygclass.html
>
Yes, I had read that.

> Try directory specification rather than path - cygport often just DTRT:
>
>         CYGCMAKE_SOURCE=cmake
>
Yes, I had also tried that, but without success.

Sincerely.

> --
> Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
>
> This email may be disturbing to some readers as it contains
> too much technical detail. Reader discretion is advised.
> [Data in binary units and prefixes, physical quantities in SI.]
>
>
> > =======> And this is the content of my liblo.cygport file:
> >
> > inherit cmake
> >
> > NAME="liblo"
> > VERSION=0.31
> > RELEASE=1
> > CATEGORY="Audio"
> > SUMMARY="Open Sound Control protocol for POSIX systems"
> > DESCRIPTION="Open Sound Control (OSC) is a protocol for communication
> >   among computers, sound synthesizers, and other multimedia devices that
> >   is optimized for modern networking technology."
> > HOMEPAGE="http://liblo.sourceforge.net/"
> > SRC_URI="http://downloads.sourceforge.net/liblo/liblo-${VERSION}.tar.gz"
> >
> > PKG_NAMES="liblo1 liblo-devel"
> > PKG_IGNORE="
> >      usr/share/doc/liblo/AUTHORS
> >      usr/share/doc/liblo/COPYING
> >      usr/share/doc/liblo/ChangeLog
> >      usr/share/doc/liblo/NEWS
> >      usr/share/doc/liblo/README
> >      usr/share/doc/liblo/TODO
> > "
> >
> > liblo1_CATEGORY="Libs"
> > liblo1_SUMMARY="${SUMMARY}"
> > liblo1_CONTENTS="
> >      usr/bin/cyglo-7.dll
> >      usr/bin/oscdump.exe
> >      usr/bin/oscsend.exe
> > "
> > liblo_devel_CATEGORY="Libs"
> > liblo_devel_SUMMARY="${SUMMARY}"
> > liblo_devel_CONTENTS="
> >      usr/include/lo/*
> >      usr/lib/liblo.dll.a
> >      usr/lib/pkgconfig/liblo.pc
> >      usr/lib/cmake/liblo/libloConfig.cmake
> > "
> >
> > CYGCMAKE_SOURCE="${S}/cmake"
>
> --
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2021-09-17  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-16 15:18 Carlo B.
2021-09-16 17:48 ` Brian Inglis
2021-09-17  8:18   ` Carlo B. [this message]
2021-09-17  9:37 ` Carlo B.
2021-09-17 15:41   ` Brian Inglis
2021-09-17 20:57     ` Carlo B.

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=CADt9574_sW83-RWjj2-gzzqt6WKMqDQM6+UdqB6F1gZRejGC5Q@mail.gmail.com \
    --to=carlo.bramini@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).