AVR Downloader/UploaDEr - Bugs: bug #36713, config assumes obsolete libusb API
You are not allowed to post comments on this tracker with your current authentication level.
bug #36713: config assumes obsolete libusb API
Submitter: | None | ||
Submitted: | Sat 23 Jun 2012 10:02:55 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Priority: | 5 - Normal | Item Group: | None |
Status: | Need Info | Privacy: | Public |
Assigned to: | None | Originator Name: | Jeff Inman |
Originator Email: | -email is unavailable- | Open/Closed: | Open |
Release: | None | Programmer hardware: | |
Device type: |
Wed 18 Sep 2013 07:27:34 AM UTC, comment #1: |
Joerg Wunsch <joerg_wunsch> |
Sat 23 Jun 2012 10:02:55 PM UTC, original submission:
If you build libusb 1.0.9, and then using that to build avrdude, you might have a config something like this (with tcsh):
|
Anonymous |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2013-09-18 | joerg_wunsch | Status | None | Need Info |
Powered by Savane 3.13-758e.
Corresponding source code
Well, not all supported platforms do offer a libusb-1.0 API.
(The last one I've heard of was/is OpenSolaris.)
All known libusb-1.0 implementations also ship with a 0.1
API compatibility wrapper. As AVRDUDE doesn't need any of
the newer 1.0 features, it is not in a real need to rewrite
everything for the 1.0 API.
Meanwhile, parts of AVRDUDE actually use the 1.0 API (those
parts will be disabled on systems that don't provide it), and
the configuration status is clearly printed at the end:
Why can't you use the 0.1 API wrapper in your case?