98b1e91f1edd220d794c7dd46
[2] https://packages.debian.org/search?keywords=fxload
[3]
http://metadata.ftp-master.debian.org/changelogs//main/f/fxload/fxload_0.0.20081013-1_changelog
[4] http://linux-hotplug.cvs.sourceforge.net/viewvc/linux-hotplug/fxload/
--
Dr. Ludovic Rousseau
---
Use https://github.com/libusb/libusb instead of libusbx. See also
http://libusb.info
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/169#issuecomment-39671890--
_
;return 0;
> --
> 1.8.5.2
Patch applied in
https://github.com/libusb/libusb/commit/93de199d8d60822fc42b1cbf8b920132cd8bbbc6
Thanks
--
Dr. Ludovic Rousseau
--
WatchGuard Dimension instantly turns raw ne
nto your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______
> libusbx-devel mailing list
> libusbx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lis
se the released libusb-1.0.18-rc1.tar.bz2 instead (unless
you know what you are doing).
Regards,
--
Dr. Ludovic Rousseau
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Ch
nd thus to errors.
> Attached is a tiny patch for a fix.
> thx..
Fixed in
https://github.com/libusbx/libusbx/commit/30747cee3f6d7dc4a98490c24fc9b8536ae79e51
Thanks
--
Dr. Ludovic Rousseau
--
Sponsored by Intel(R)
@Lekensteyn by ``_unicode`` you mean UTF-8? UTF-16? UTF-32? or something else ?
:-)
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/156#issuecomment-27806424--
November Webin
s (LANGIDs)" [1]
but I am looking for a computer version of the file. Most preferably
in Python.
Any suggestion?
Thanks
[1] http://www.usb.org/developers/docs/USB_LANGIDs.pdf
--
Dr. Ludovic Rousseau
--
Octobe
fixed in 28d5514e61ca7f7459c200b187b8cc3ebeda9274
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/149#issuecomment-25296304--
October Webinars: Code for Performance
Free Int
Closed #149.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/149--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance
Fixed in c4f2c353b9a1f6bc418dcd1d330d7c99084570d5 and previous patches
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/142#issuecomment-25295616--
October Webinars: Code for P
Closed #142.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/142--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Closed #148.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/148--
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Fixed in d09389be6f91f5e6a382a90f68916e8ee7444a60
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/148#issuecomment-25295427--
October Webinars: Code for Performance
Free Intel
Hello,
I propose some fixes in https://github.com/libusbx/libusbx/pull/142
If no objection in the next few days I will push them upstream.
The problems were reported by the Coverity scan tool. Some other
problems still need to be fixed.
Bye
--
Dr. Ludovic Rousseau
Fix some problems reported by the Coverity scan tool
You can merge this Pull Request by running:
git pull https://github.com/LudovicRousseau/libusbx fixes
Or you can view, comment on it, or merge it online at:
https://github.com/libusbx/libusbx/pull/142
-- Commit Summary --
* examples: c
Fixed in e2babf7ec295bde9d0b04fe1c325131dc6aacf51
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/141#issuecomment-24888525--
LIMITED TIME SALE - Full Year of Microsoft Traini
Closed #141.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/141--
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including Vis
trick (or workaround) to suppress the message ?
Are you using libusb-compat?
if yes, can't you switch to libusbx directly?
Bye
--
Dr. Ludovic Rousseau
--
LIMITED TIME SALE - Full Year of Microsoft Training For Ju
You can merge this Pull Request by running:
git pull https://github.com/LudovicRousseau/libusbx fixes
Or you can view, comment on it, or merge it online at:
https://github.com/libusbx/libusbx/pull/141
-- Commit Summary --
* examples: Fix a memory leak
* examples: Fix a memory leak
--
Hello,
The Coverity tool reported many memory leaks in examples/ezusb.c
I fixed them in the attached patches (also available as
https://github.com/libusbx/libusbx/pull/141)
If no objections I will push them this nexy week-end.
Bye
--
Dr. Ludovic Rousseau
0001-examples-Fix-a-memory
it from libusb-1.0 with no code
change. We should not break this "contract".
So I think the best is to keep the resource leak and avoid crashes.
Bye
--
Dr. Ludovic Rousseau
--
Learn the latest--Visual Stu
verity and ask to join the libusbx project. I will add you. The
service if free (as in free beer).
I use Coverity as _another_ static analysis tool for my free software projects.
Bye
[1] https://scan.coverity.com/
--
Dr. Ludovic Rousseau
CID,Type,Impact,Status,First Detected,Owner,Classificatio
2013/8/22 Brilliantov Kirill Vladimirovich :
> Ludovic Rousseau wrote on 08/21/2013 06:29 PM:
>
>>
>> This should already be fixed upstream in
>> https://github.com/libusbx/libusbx/commit/83021abc20102e45f0eab53a3bea92279259182a
>>
>> Can you check your problem
patch (720 B)), run
> autoreconf -i and after this I build library.
This should already be fixed upstream in
https://github.com/libusbx/libusbx/commit/83021abc20102e45f0eab53a3bea92279259182a
Can you check your problem is fixed in the currrent git version?
Bye
--
Dr. Ludovic Rousseau
online Doxygen documentation.
Did we missed this step for the 1.0.16 release?
Bye
[1]
https://github.com/libusbx/libusbx/wiki/Maintainers%27-Corner#wiki-RCRelease_work
--
Dr. Ludovic Rousseau
--
Introducing Performance
Can you merge all your 6 commits into only 1 please?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/134#issuecomment-22958234
--
Introducing Performance Central, a new site f
rything renamed except references to libusbx.org.
What is your sourceforge account so I can add you?
Bye
--
Dr. Ludovic Rousseau
--
Introducing Performance Central, a new site from SourceForge and
AppDynamics. Performance
The pull request still contains 56 commits. So something is not working as
expected.
Please create a new pull request and close this one.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/128#issuecomment-22654142
-
You now need to push you rebased branch to update this pull request (or maybe
open a new and clean pull request).
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/pull/128#issuecomment-22595385
--
The first thing you should do is ``git rebase upstream/master``, fix any
conflict and then push your policy branch (maybe using --force).
This should remove a lot of the patches already upstreamed and will simplify a
lot the review.
---
Reply to this email directly or view it on GitHub:
https:/
One of the goals of systemd is to _merge_ ``/lib`` with ``/usr/lib`` not to
separate them even more. See
http://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
So I am very surprised to get this request _because_ of systemd.
I think this request is should be ignored and closed
I am sorry I can't parse your patch. Please fork libusbx and commit your patch
in a branch so we can review it.
Question 1: why do you want to install libusbx in ``/lib`` instead of
``/usr/lib``?
Question 2: what is wrong with ``--libdir=/lib``?
---
Reply to this email directly or view it on Gi
Closed #84.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/84
--
Get your SQL database under version control now!
Version control is standard for application code, but data
The Xcode project support is now added. Closing.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/84#issuecomment-21996116
--
Get your SQL database under version control now!
2013/8/2 Hans de Goede :
> Hi,
>
>
> On 08/02/2013 10:51 AM, Ludovic Rousseau wrote:
>>
>> Hello,
>>
>> I have not seen a discussion about this patch.
>> I think it is correct and should be applied.
>>
>> Comments?
>
>
> I agree it is
u=/4140/ostg.clktrk
> _______
> libusbx-devel mailing list
> libusbx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libusbx-devel
--
Dr. Ludovic Rousseau
--
2013/8/1 Sean McBride :
> On Thu, 1 Aug 2013 06:28:27 +0200, Ludovic Rousseau said:
>
>>I still have 2 commits from Sean in my Xcode branch:
>>
>>- Core: defensive programming
>>https://github.com/LudovicRousseau/libusbx/commit/
>>5da4949cffacf1a19aeaf62ce796019
t Xcode related. Maybe we can drop it.
- README: Add OS X specific notes about the lack of libtoolize
https://github.com/LudovicRousseau/libusbx/commit/550cae08c109f1e6257f341f13345219caeb69d0
Add some documentation on how to build libusbx on Mac OS X
I think the second patch
What are the automake 1.14 warnings?
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/125#issuecomment-21709028
--
See everything from the browser to the database with AppDyn
t; is used instead)
I don't remember a discussion about this problem before.
Nathan (and the others), can you post your comments at github instead
of replying to the mailing list for github issues?
Thanks
[1] https://github.com/libusbx/libusbx/issues/121#issuecomment-21386772
--
Dr. L
> This is micro-optimization, of course, but it would be more efficient to
> do this instead:
> fputs(str, stderr);
I also agree. Maybe Pete missed your email.
Attached is the commit for this change.
Bye
--
Dr. Ludovic Rousseau
0001-Core-use-fputs
Hello,
A small patch for:
strerror.c: In function 'libusb_setlocale':
strerror.c:148: warning: comparison between signed and unsigned
strerror.c:152: warning: comparison between signed and unsigned
--
Dr. Ludovic Rousseau
0001-Core-fix-compiler-warning-in-libusb_setlocale.patch
D
ue with HIDAPI?
Why do you want to use libusbx instead?
> Is it possible ? and in that case could someone direct me on where to start
> ?
Have you read
https://github.com/libusbx/libusbx/wiki/FAQ#wiki-Does_libusbx_support_HID_devices?
reproduce the problem here (Debian stable + libusbx git version).
Can you rebuild and retest with debug messages?
Bye
--
Dr. Ludovic Rousseau
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
h
2013/6/10 Ludovic Rousseau :
> Hello,
>
> Two \n are missing in error messages from examples/xusb
Patch attached
--
Dr. Ludovic Rousseau
0001-Examples-add-a-missing-n-at-end-of-error-messages.patch
Description: Bi
will push it "soon" in the official repository.
Bye
--
Dr. Ludovic Rousseau
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashb
eck the value returned by libusb_setlocale()
Proposal:
- call libusb_setlocale() _only_ when the 'l' argument is used
- display the error message if libusb_setlocale() fails
Code proposal:
case 'l':
r = libusb_setlocale(argv[++j]);
if (r != LIBUSB_SUCCESS) {
2013/6/8 Pete Batard :
> On 2013.06.08 16:39, Ludovic Rousseau wrote:
>> If you don't want to invest more time than needed then just provide
>> the missing MSVC and mingw changes.
>> But you _also_ had time to rewrite a working code.
>
> Indeed. The choice was: D
req feature, next time I'll do it manually.
Should we change the history and reapply the patches using the correct
procedure?
I volunteer to do the job.
--
Dr. Ludovic Rousseau
--
How ServiceNow helps IT people
mething into a bounded array index to reference array data.
If you don't want to invest more time than needed then just provide
the missing MSVC and mingw changes.
But you _also_ had time to rewrite a working code.
bikeshedding
http://en.wiktionary.org/wiki/bikesh
2013/6/7 Pete Batard :
> How does that sound? I can produce a formal patch if you like this
> solution enough.
It is too late to rewrite exiting and working code.
Unless you have a lot of free time :-)
And I prefer Hans version.
Bye
--
Dr. Ludovic Ro
2013/6/6 Hans de Goede :
> I've merged the pull request into master. Ludovic, this should fix your
> problem, please test.
Problem fixed.
Thanks
--
Dr. Ludovic Rousseau
--
How ServiceNow helps IT people t
_0_la-poll_posix.lo'. Stop.
The file os/poll_posix.c is not present in the repository.
Where am I supposed to find the official/supported Mac OS X version of libusbx?
Thanks
--
Dr. Ludovic Rousseau
--
How Servic
, iso639[i]) == 0)
> + break;
> + }
> + if (!iso639[i]) {
> + usbi_warn(NULL, "Unsupported language: %s", lang);
> + return LIBUSB_ERROR_NOT_FOUND;
> + }
> +
> + libusb_locale = i;
> +
> + re
2013/6/3 Pete Batard :
> On 2013.06.01 12:57, Ludovic Rousseau wrote:
>> Only one libusb.pc file can be installed at a given time.
>>
>> I will take an example with a foo library on Linux.
>> The libfoo-x.y.z.tar.gz archive when build will provide the files
>>
2013/6/1 Pete Batard :
> On 2013.05.31 08:57, Ludovic Rousseau wrote:
>> Another proposal is to remove the version number from the .pc file.
>
> Well, it sure looks like dead weight to me.
>
>> On my Debian system I have:
>> $ ls -l /usr/lib/x86_64-linux-gnu/pkgconfi
part of the library version but part of the library
name. And we can't change the library name, unless we want to provide
a completely different library.
To summarise:
For libusb-1.2
- do not change the libusb-1.0.pc name
- do not c
e by case decision.
For gettext the license is GNU GPL v2+. See [1].
So gettext is not an option for libusbx.
Bye
[1] http://savannah.gnu.org/projects/gettext/
--
Dr. Ludovic Rousseau
--
Introducing AppDynamics Lite, a
won't have), and slow and expensive io to the device, which
> includes waking it up from sleep, thus burning battery on portable devices.
OK. I understand now.
I agree with the new calls libusb_get_vendor_string/lib
num libusb_error errcode,
> const char *locale);
> ?
Because very few people will need to change the locale parameter for
different calls to libusb_strerror()?
Because it is adding complexity to the API comprehension?
Because the API will not look like the ISO C99 strerror(3) function any more?
okup. Beyond that,
> this becomes a maintenance headache.
Maybe it is time to start a new library that would be a libusb
companion with "higher" level functions or helper functions.
> However, I may not be in the majority. I also think the pro
) the returned string.
> + *
> + * \param errcode the error code whose description is desired
> + * \returns a short description of the error code in UTF-8 encoding
> + */
> +DEFAULT_VISIBILITY const char* libusb
- compile with clang on 10.8 and test on 10.8
> the user have installed XCode 3.something (the last available for 10.6),
> compiled the lib for both 32 and 64 bits and this one does not segfault.
> I thought you must knew.
Can you also perform the tests I suggested abo
1
>
>
> Does the user need to install XCode in order to compile libusbx to see if I
> fail at compilation?
If the compilation succeeds it should be OK.
You can add debug information by adding "-g":
CFLAGS="-g ..."
We can then get some more debug information in the c
2013/4/23 Pete Batard :
> On 2013.04.23 10:21, Ludovic Rousseau wrote:
>> The API [1] should be updated but I don't yet know how to do that.
>
> As per https://github.com/libusbx/libusbx/wiki/Maintainers%27-Corner:
> o Run make docs-upload in the /doc directory
Exact. S
gt; * on all devices in the list. libusb_open() adds another reference which is
> --
> 1.8.2
Pushed.
Thanks
The API [1] should be updated but I don't yet know how to do that.
[1]
http://libusbx.sourceforge
e people trying to
>> infer the license from these rather than the source)
>>
>> If you can satisfy 1 & 2, since I explained that I don't want to care
>> about this crap, and send a patch, I'll have no quibble a
1755:30: note: remove constant to silence this warning
> return (usbi_backend->caps && USBI_CAP_HAS_HID_ACCESS);
> ~^~
>
It is not just a warning but a real bug.
libusb_has_capability() could _n
2013/3/25 Hans de Goede :
> Hi,
>
>
> On 03/23/2013 12:05 PM, Ludovic Rousseau wrote:
>>
>> 2013/3/23 Hans de Goede :
>>>
>>> We all seem to agree on that, which is good :) So it would be helpful
>>> to get some feedback on my proposed API for th
to the parameter value instead
of using 1.
Something like LIBUSB_AUTO_DETACH_KERNEL_DRIVER_ENABLE
I don't know if we also need a LIBUSB_AUTO_DETACH_KERNEL_DRIVER_DISABLE
If not maybe the parameter can be removed.
Or maybe the function can be named:
libusb_set_parameter(handle, LIBUSB_AU
2013/3/22 Hans de Goede :
> Hi,
>
>
> On 03/22/2013 10:58 AM, Ludovic Rousseau wrote:
>>
>> 2013/3/22 Hans de Goede :
>>>
>>> Although automatic detaching may seem like a smart and user (programmer)
>>> friendly thing to do, I'm
.
So I propose to NOT add an automatic detach.
Bye
[1]
http://libusb.6.n5.nabble.com/Automatic-detach-of-a-HID-device-using-udev-Re-How-to-dump-HID-report-descriptor-under-Linux-td3330260.html#a3334978
--
Dr. Ludovic Rousseau
---
r _any_ error code returned by
libusb_claim_interface()
But maybe that is not possibe to return such a specific error code.
Bye
[1] https://github.com/libusbx/libusbx/blob/master/examples/xusb.c#L836
--
Dr. Ludovic Rousseau
Do we need to have plateform specific code to detach the driver (if
needed) on Linux?
What would a real program look like?
Thanks,
--
Dr. Ludovic Rousseau
--
Everyone hates slow websites. So do we.
Make your web apps fast
ting
Bye
--
Dr. Ludovic Rousseau
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdy
2013/2/17 Pete Batard :
> On 2013.02.16 17:50, Ludovic Rousseau wrote:
>> ../../libusb/os/threads_windows.c:137:1: warning: '__inline' is not at
>> beginning of declaration [-Wold-style-declaration]
>
> The compiler's probably right on that one. Easy to fix.
2013/2/17 Pete Batard :
> On 2013.02.16 17:50, Ludovic Rousseau wrote:
>> I installed MinGW on Debian. And the compiler reported warnings and
>> potential bugs.
>
> Because you're using pedantic options, right?
No. Not yet :-)
> Can you provide the extra compiler o
ning: nested extern
declaration of 'epoch_time' [-Wnested-externs]
Bye
[1] https://github.com/libusbx/libusbx/pull/86
--
Dr. Ludovic Rousseau
--
The Go Parallel Website, sponsored by Intel - in partnership with
I prefer to fix only one problem in one patch.
It is then easier to find a bug using "git bisect" for example.
Thanks for merging the code.
Bye
--
Dr. Ludovic Rousseau
--
Master Visual Studio, SharePoint
in the public libusb.h
5- we should use a flexible array member [1] with a C99 compiler. Is
MSVC C99 comliant?
Bye
[1] http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Zero-Length.html
--
Dr. Ludovic Rousseau
--
Master Vis
es" branch
instead of my "master" branch.
Bye
[1] https://github.com/libusbx/libusbx/pull/70
--
Dr. Ludovic Rousseau
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, Jav
. Ludovic Rousseau
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and
much more. Get web development skills now with LearnDevNow -
350+ hours of step-by-step video tutorials by Microsoft MVPs and experts
is for Windows so should be in a
Windows only file.
Or maybe add a #ifdef WIN32 (or similar) so it is a Windows only configuration?
Bye
--
Dr. Ludovic Rousseau
--
Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js,
libusbx/commit/cf6e68acb116c63f4a8c9d30ee4f2757e8c2e12a
>
> It moved the setting of usbi_default_context to earlier in the method, but
> didn't increment the reference count.
>
> I've attached a patch to fix the issue.
This patch fixes the crash.
Pull request at https://
ady destroyed.
The test comment is exact:
/** Tests that the default context (used for various things including
* logging) works correctly when the first context created in a
* process is destroyed. */
The answer is that it does not work.
Does this test pass on
ress test in
this case).
These stress test programs should NOT be used as example by our users. We
should try to avoid possible confusion where we can.
It can be the beginning of a more complete test suite :-)
Bye
--
Dr. Ludovic Rousseau
--
2012/11/1 Xiaofan Chen :
> On Thu, Nov 1, 2012 at 4:19 PM, Ludovic Rousseau
> wrote:
>> I mostly agree. But: :-)
>> - the default is then to build a 32-bits library on my 64-bits system.
>> I don't know why.
>> - Xiaofan complained that only one architecture was
2012/10/31 Sean McBride :
> On Wed, 31 Oct 2012 20:07:17 +0100, Ludovic Rousseau said:
>
>>You missed my latest change about build for 32 and 64 bits :-(
>>
>>I propose to add to Xcode/common.xcconfig:
>>ARCHS = $(ARCHS_STANDARD_32_64_BIT)
>>
>>Or mayb
4 bits :-(
I propose to add to Xcode/common.xcconfig:
ARCHS = $(ARCHS_STANDARD_32_64_BIT)
Or maybe there is a better place for this setting.
Bye
--
Dr. Ludovic Rousseau
--
Everyone hates slow websites. So do we.
Make your web app
2012/10/31 Xiaofan Chen :
> On Wed, Oct 31, 2012 at 12:55 AM, Ludovic Rousseau
> wrote:
>> It is not (or no more) specific to Mountain Lion.
>> I just tried the github code on Snow Leopard using Xcode 4.2 and it
>> builds without problem.
>>
>> Please resynch t
t; OS X 10.5).
>
> If you can come out with a universal Xcode project working for
> Mac OS X 10.5 and later, that would be good. But I know
> next to nothing about Xcode myself.
I do not have Xcode 3.x or Leopard (10.5) any more.
If I remember correctly the Xcode project format (t
2012/10/25 Sean McBride :
> On Fri, 12 Oct 2012 23:40:46 +0200, Ludovic Rousseau said:
>
>>To make Xcode happy I had to use #include "libusb.h" instead of
>>#include for local headers.
>
> As I said, I had to do the same. Now, for my own development & tes
2012/10/17 Xiaofan Chen :
> On Wed, Oct 17, 2012 at 1:46 AM, Ludovic Rousseau
> wrote:
>> 2012/10/16 Sean McBride :
>>> On Tue, 16 Oct 2012 07:41:43 +0800, Xiaofan Chen said:
>>>
>>>>Thanks. A few more issues. I do not quite understand 1),
>>>
ned as
int poll(struct pollfd fds[], nfds_t nfds, int timeout)
The timeout needs to be an int. The problem is that to calculate this
int value the libusbx code manipulates a tv_sec.
On Mac OS X tv_sec is a __darwin_time_t which is a long, not an int.
This discussion is just to fix a minor compil
2012/10/15 Sean McBride :
> On Sat, 13 Oct 2012 20:35:24 +0200, Ludovic Rousseau said:
>
>>> /Users/xiaofanc/work/libusbx/ludovic/libusbx/libusb/io.c:1877:35:
>>> Implicit conversion loses integer precision: 'long' to 'int'
>>> timeout_ms
ntain (*), and then you have
> your hands free to start working towards a 2.0 release on git master.
I also agree.
Please wait until version 2.0 to introduce the "minor"/non fundamental
API changes.
Bye
--
Dr. Ludovic Rousseau
--
waited until version 1.1 or 2.0 of libusbx
before making this API change.
Maybe we should release RIGHT NOW a 1.0.14 version of libusbx with
just the API change reverted and postpone the change to version 1.1 or
2.0.
At that time (version 1.1 or 2.0) it will be more clear that libu
cases. I think that is what we (should) want.
Bye
--
Dr. Ludovic Rousseau
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubl
e to change doxygen.cfg.in and use:
QUIET = YES
So that only warnings are displayed and are more easy to see.
I also propose to use:
WARN_NO_PARAMDOC = YES
> [1]
> http://libusbx.sourceforge.net/api-1.0/group__misc.html#gaa83ecded256e
1 - 100 of 165 matches
Mail list logo
