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 11:37:59 +0200	[thread overview]
Message-ID: <CADt9575jJ8ZvaN4+U5d=Jws=ZPooBbm13p8OLAo-YU2Y69g5Tg@mail.gmail.com> (raw)
In-Reply-To: <CADt9577MRdgv+FtGj_2py=Y+fVw+UOJCaux7P=7gHmHReAKcmQ@mail.gmail.com>

Hello,
in addition to my previous message, I did some experiments with the
code of cygport and I added these lines to
/usr/share/cygport/cygclass/cmake.cygclass:

echo "CYGCMAKE_SOURCE=${CYGCMAKE_SOURCE}"
echo "B=${B}"
echo "S=${S}"
echo "PWD=${PWD}"

and the result is:

CYGCMAKE_SOURCE=/cmake
B=/home/carlo/liblo.src/liblo-0.31-1.x86_64/build
S=/home/carlo/liblo.src/liblo-0.31-1.x86_64/src/liblo-0.31
PWD=/home/carlo/liblo.src/liblo-0.31-1.x86_64/build
*** ERROR: cygcmake: cmake directory not found

But ${CYGCMAKE_SOURCE} was set as:

CYGCMAKE_SOURCE="${S}/cmake"

So, it seems to me that there is at least a bug into the
documentation, because ${CYGCMAKE_SOURCE} does not seem to allow the
use of {S}.
I was able to make it working by writing:

CYGCMAKE_SOURCE="$(pwd)/${NAME}-${VERSION}-${RELEASE}.${ARCH}/src/${NAME}-${VERSION}/cmake"

but I don't know if this is the right way to do it and could be accepted or not.

Sincerely.

Il giorno gio 16 set 2021 alle ore 17:18 Carlo B.
<carlo.bramini@gmail.com> ha scritto:
>
> Hello,
> I'm trying to make a package for CYGWIN to provide liblo, but I'm
> having some difficulties.
> This library is available to the most used linux distributions (but
> not limited to), here there is the link to the one into a Debian as
> example:
>
> https://packages.debian.org/buster/liblo-dev
>
> I implemented a script for cygport but this is the output on the
> console when I execute it:
>
> $ cygport liblo.cygport all
> >>> Preparing liblo-0.31-1.x86_64
> >>> Unpacking source liblo-0.31.tar.gz
> >>> Preparing working source directory
> >>> Compiling liblo-0.31-1.x86_64
> *** ERROR: cygcmake: cmake directory not found
>
> The unique aspect of this library is that the CMakeLists.txt file is
> not into the root of the source tree, but it is located into a
> subfolder, see here:
>
> https://github.com/radarsat1/liblo/tree/master/cmake
>
> So, in my script, I configured ${CYGCMAKE_SOURCE} to point there, but
> it still cannot make it working. Since it seems that I'm not able to
> make it working in any way, I'm wondering if the behaviour of this
> variable has been ever tested, so I'm writing here with the hope to
> receive a suggestion.
>
> Thank you very much for your support.
>
> =======> 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"

  parent reply	other threads:[~2021-09-17  9:38 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.
2021-09-17  9:37 ` Carlo B. [this message]
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='CADt9575jJ8ZvaN4+U5d=Jws=ZPooBbm13p8OLAo-YU2Y69g5Tg@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).