unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Help with package AppImage support
Date: Mon, 29 Nov 2021 12:48:04 +0000	[thread overview]
Message-ID: <TiRxpnSTz_cfbX4JtWxu2P9vgSsDEyRP5Ok-z_AcW1wCS45YD-TahAcxIi5t1j8g9E1ijVXQsWE590b5x9JEofrvbfh1zm0QZSAs7dd3VHE=@elenq.tech> (raw)
In-Reply-To: <877dcsnjkh.fsf@elephly.net>

Hi Ricardo,


> Ekaitz Zarraga <ekaitz@elenq.tech> writes:
>
> >> Maybe “TARGET NOT found” is CMake’s original way of saying that
> >> you’re
> >> missing a dependency (libsquashfuse), no?
> >
> > I mean, I already reached that conclusion but if you check the
> > packages in the
> > original message, the dependency is included. I can't find why
> > isn't it finding
> > the library.
> >
> > I need there some help making CMake find the dependency I
> > already included and
> > packaged.
>
> Does the CMakeLists.txt or the files under cmake/ mention
> libsquashfuse?  There should either be a Find* macro that
> describes the tests CMake will perform to determine certain
> variables for using libsquashfuse, or it will use a conventional
> way to do that: via pkg-config or using .cmake files in
> libsquashfuse.
>
> So there coulde be different problems here: libsquashfuse doesn’t
> install the expected cmake files or installs them in the wrong
> place; or this package tells CMake to search using pkg-config but
> you don’t have pkg-config among the inputs; or this is all the
> case and pkg-config fails because a library isn’t propagated when
> it should be, etc.

All packages use pkg-config as a native input.

This is the directory structure of squashfuse. It doens't include the Find* but
it contains a pkgconfig file. I'm not sure if it's located in the correct
path though.

--8<---------------cut here---------------start------------->8---

/gnu/store/3ksjpfy6lma86b03fal3n0q1zfm1l9v2-squashfuse-0.1.104
├── bin
│   ├── squashfuse
│   └── squashfuse_ll
├── include
│   └── squashfuse
│       ├── cache.h
│       ├── common.h
│       ├── config.h
│       ├── decompress.h
│       ├── dir.h
│       ├── file.h
│       ├── fs.h
│       ├── squashfs_fs.h
│       ├── squashfuse.h
│       ├── stack.h
│       ├── table.h
│       ├── traverse.h
│       ├── util.h
│       └── xattr.h
├── lib
│   ├── libsquashfuse.a
│   ├── libsquashfuse.la
│   ├── libsquashfuse.so -> libsquashfuse.so.0.0.0
│   ├── libsquashfuse.so.0 -> libsquashfuse.so.0.0.0
│   ├── libsquashfuse.so.0.0.0
│   └── pkgconfig
│       └── squashfuse.pc
└── share
    ├── doc
    │   └── squashfuse-0.1.104
    │       └── LICENSE
    └── man
        └── man1
            └── squashfuse.1.gz
--8<---------------cut here---------------end--------------->8---

> The first step should be to figure out if CMake uses one of these
> Find* macros or some other way.  If it’s a Find* macro, determine
> if it is provided by libsquashfuse or appimagekit.

This is the only reference I find to squashfuse so I don't know what's the
mechanism they are doing. In cmake/dependencies.cmake they are not searching
for squashfuse neither...
https://github.com/AppImage/AppImageKit/blob/8bbf694455d00f48d835f56afaa1dabcd9178ba6/src/build-runtime.cmake#L18


Thanks for the help,
Ekaitz


  reply	other threads:[~2021-11-29 12:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 14:29 Help with package AppImage support Ekaitz Zarraga
2021-11-23 17:19 ` Ludovic Courtès
2021-11-23 19:12   ` Ekaitz Zarraga
2021-11-28 17:29     ` Ludovic Courtès
2021-11-28 17:38       ` Ekaitz Zarraga
2021-11-28 19:49         ` Ricardo Wurmus
2021-11-29 12:48           ` Ekaitz Zarraga [this message]
2021-11-29 13:20             ` Ricardo Wurmus
2021-11-29 14:27               ` Ekaitz Zarraga
2021-11-29 15:06                 ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='TiRxpnSTz_cfbX4JtWxu2P9vgSsDEyRP5Ok-z_AcW1wCS45YD-TahAcxIi5t1j8g9E1ijVXQsWE590b5x9JEofrvbfh1zm0QZSAs7dd3VHE=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).