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 14:27:46 +0000	[thread overview]
Message-ID: <6NBnXP97_7J_hgPlHbuSkeqe6_Glf89hmXzjjgLhRonSY9cji-e1uDeDsXfIhq5biF6jpAFyE8wQnnEqWvOxZtZ7FYG7YGglMYA_tT6ISg8=@elenq.tech> (raw)
In-Reply-To: <87czmjm726.fsf@elephly.net>

Hi Ricardo,

> appimagekit includes a copy of libappimage; that repository
> contains a Findsquashfuse.cmake file, which defines how squashfuse
> is found:
>
> https://github.com/AppImage/libappimage/blob/13f401a4a384ec59ec9a144e2a7006adf751571f/cmake/Modules/Findsquashfuse.cmake
>
> Ricardo

I see what's going on now.

I unbundled libappimage from appimage kit and added it as a dependency so
there's no way to find libsquashfuse in appimagekit because it tries to use the
bundled lib I removed.

So I'm not sure what to do right now to be honest. This way to bundle
everything makes me mad... All this packages are mixed together in a way that
is hard to separate... :S

Thanks for the info now I know why was all this happening! I was completely
lost with the "target not found" issue because I didn't know where was it
coming from!

Ekaitz



  reply	other threads:[~2021-11-29 14:35 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
2021-11-29 13:20             ` Ricardo Wurmus
2021-11-29 14:27               ` Ekaitz Zarraga [this message]
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='6NBnXP97_7J_hgPlHbuSkeqe6_Glf89hmXzjjgLhRonSY9cji-e1uDeDsXfIhq5biF6jpAFyE8wQnnEqWvOxZtZ7FYG7YGglMYA_tT6ISg8=@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).