On 12/08/13 03:41, Xiaofan Chen wrote:
On Fri, Aug 9, 2013 at 6:51 PM, Toby Gray wrote:
If you are planning on testing on a device then you'll need to have root
access to it or fiddle around with building custom ROMs to setup
permissions on /dev/bus/usb/*/*.
Also be aware that the Android dyna
On Mon, Aug 12, 2013 at 8:08 PM, Toby Gray wrote:
> I assume it'd be helpful for others to have this information recorded
> somewhere. Would a wiki page or an update to the README be
> more appropriate?
I think Android has become so popular that a README.Android
is good to have.
--
Xiaofan
---
Yes you are right. This is still in libusbx.git. The project file needs to be
updated.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22489846
--
Get 100%
BTW, the VS2012 files are good in this aspect.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22491895
--
Get 100% visibility into Java/.NET code with AppD
Just tried VS2012 under Windows 8 and there is a warning
for latest git tree. It is probably better to fix this as well for
1.0.17 release.
..\libusb\os\windows_usb.c(1768): warning C4267: 'return' : conversion
from 'size_t' to 'int', possible loss of data
--
Xiaofan
-
This is a bit too much to digest, as far as I'm concerned. Unless you can
submit your changes as patches that apply cleanly on top of the latest libusbx,
it's unlikely that we are going to spend a lot of time looking at them. There's
just too much work involved in doing that and our resources ar
On 2013.08.12 14:15, Xiaofan Chen wrote:
> Just tried VS2012 under Windows 8 and there is a warning
> for latest git tree. It is probably better to fix this as well for
> 1.0.17 release.
>
> ..\libusb\os\windows_usb.c(1768): warning C4267: 'return' : conversion
> from 'size_t' to 'int', possible lo
I'll just point out that I don't believe anybody is testing the project with
VS2010 any longer. As far as I'm concerned, I'm using VS2012 exclusively for
Visual Studio, and I have no plans to test earlier versions of Visual Studio,
so most of these projects update come from copy/paste and manual
Closed #129 via d28ab4bf13eb101f35d3543a3b2c2ca51a98e19d.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129
--
Get 100% visibility into Java/.NET code with AppDynamics Lit
On Mon, Aug 12, 2013 at 4:40 PM, Pete Batard wrote:
> This is a bit too much to digest, as far as I'm concerned. Unless you can
> submit your changes as patches that apply cleanly on top of the latest
> libusbx, it's unlikely that we are going to spend a lot of time looking at
> them. There's just
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:/
On Tue, Aug 13, 2013 at 4:45 AM, Pete Batard wrote:
> On 2013.08.12 14:15, Xiaofan Chen wrote:
>> Just tried VS2012 under Windows 8 and there is a warning
>> for latest git tree. It is probably better to fix this as well for
>> 1.0.17 release.
>>
>> ..\libusb\os\windows_usb.c(1768): warning C4267:
I think you forget to update libusb_dll_2010.vcxproj.filters as well.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129#issuecomment-22533621
--
Get 100% visibility into
Reopened #129.
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/129
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designe
BTW, I think it is perfectly okay for you to mention that you only test VS2012.
I do not use VS much myself. And I think we may want to drop MSVC 6.0 support
since I think it is too old to support. And even VS2005 is quite old but
probably it is also for VS2008 users.
---
Reply to this email di
15 matches
Mail list logo
