From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add dfu-programmer
Date: Mon, 29 Sep 2014 18:09:26 +0200 [thread overview]
Message-ID: <87bnpyv26h.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzN8U88Pu=1yyH_VMjPP7ExmvQJc4x7LEbx5WeGJMKqCDQ@mail.gmail.com> (Manolis Ragkousis's message of "Mon, 29 Sep 2014 13:46:04 +0300")
Manolis Ragkousis <manolis837@gmail.com> skribis:
> From 8f0da7d367be1995f8980992a647adedd85d2f1c Mon Sep 17 00:00:00 2001
> From: Manolis Ragkousis <manolis837@gmail.com>
> Date: Mon, 29 Sep 2014 13:27:30 +0300
> Subject: [PATCH] gnu: Add dfu-programmer
>
> * gnu/packages/dfu-programmer.scm: New file
> * gnu-system.am (GNU_SYSTEM_MODULES): Add dfu-programmer.scm
> * gnu/packages/patches/dfu-programmer-fix-libusb.patch: New patch.
> * gnu-system.am (dist_patch_DATA): Add it.
As discussed on #guix, it might be good to move it to a ‘flashing-tools’
module or something?
> + (home-page "http://dfu-programmer.github.io/")
> + (synopsis "Dfu-programmer for Atmel chips")
Rather “Device firmware update programmer for Atmel chips”.
> + (description
> + "Dfu-programmer is a multi-platform command-line programmer for Atmel (8051, AVR, XMEGA & AVR32)
> + chips with a USB bootloader supporting ISP")
Please wrap lines to less than 80 chars.
> +--- a/src/dfu-device.h
> ++++ b/src/dfu-device.h
> +@@ -6,7 +6,7 @@
> + #endif
> + #include <stdint.h>
> + #ifdef HAVE_LIBUSB_1_0
> +-#include <libusb.h>
> ++#include <libusb-1.0/libusb.h>
I think the bug is rather that pkg-config is missing, because libusb.pc
has this line:
Cflags: -I${includedir}/libusb-1.0
Could you try adding it as a native input and report back?
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-09-29 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 10:46 [PATCH] gnu: Add dfu-programmer Manolis Ragkousis
2014-09-29 16:09 ` Ludovic Courtès [this message]
2014-10-01 6:22 ` Manolis Ragkousis
2014-10-02 8:47 ` Ludovic Courtès
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=87bnpyv26h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=manolis837@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.