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 22:57:18 +0200 [thread overview]
Message-ID: <CADt9577j6yO39h2+zgPqwdebww0m1OooTEjKB8iSpUVquSqtYw@mail.gmail.com> (raw)
In-Reply-To: <fed7b366-56ef-0a93-1b8b-fbb8c6ced443@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
Hello,
> If you look at the Cygport Install Functions docs for docinto, ...into,
> defining target directories, you would see that an "absolute" path
> disables cygport from prefixing a subdirectory name with the package
> name, etc. so CMakeLists.txt is (linked) under ${S,B}/cmake, and cygport
> will automatically find that, so it should not be required or specified:
>
> https://cygwin.github.io/cygport/cmake_cygclass.html#robo767
>
cygport does not find it.
If CYGCMAKE_SOURCE is not defined into my liblo.cygport, it prints:
*** ERROR: cygcmake: cmake directory not found
If CYGCMAKE_SOURCE is defined as "${S}/cmake", it prints again:
*** ERROR: cygcmake: cmake directory not found
If CYGCMAKE_SOURCE is defined as an absolute path like I have written
in my previous message, it finally works.
> "This is only necessary when the top-level CMakeLists.txt is not in $S
> and cygcmake is not being run in the same subdirectory of $B which under
> $S contains the top-level CMakeLists.txt. (IOW if the top-level
> CMakeLists.txt is in $S/unix and cygcmake is run from $B/unix, setting
> CYGCMAKE_SOURCE would not be necessary.)"
"This is only necessary when the top-level CMakeLists.txt is not in $S"
true, it is under "$S/cmake"
"and cygcmake is not being run in the same subdirectory of $B which
under $S contains the top-level CMakeLists.txt."
also true in my opinion.
It could be possible that I have not understood something, but however
there is also an easy way:
- my cygport file was included in my first email and also attached
into this last one.
- the source archive can be downloaded from this direct link:
http://downloads.sourceforge.net/liblo/liblo-0.31.tar.gz
- put both them into a directory and execute:
cygport liblo.cygport all
and you will see with your eyes that it does not work.
Perhaps, there are other extra things to write in my cygport that I
don't know about.
thank you very much for your support.
Sincerely.
[-- Attachment #2: liblo.cygport --]
[-- Type: application/octet-stream, Size: 1002 bytes --]
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"
prev parent reply other threads:[~2021-09-17 20:57 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.
2021-09-17 15:41 ` Brian Inglis
2021-09-17 20:57 ` Carlo B. [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=CADt9577j6yO39h2+zgPqwdebww0m1OooTEjKB8iSpUVquSqtYw@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).