Le lundi 31 août 2009 à 20:05 -0400, Chris Frey a écrit : > Hi Nicolas, > > I've merged your bjdwp tree into Barry today, with a few modifications.
Thank's I'm going to update my repository... > One question: I notice there is a bjdwp directory under doc, and a > doc directory under the root bjdwp... is it safe to remove one of these? > If so, please remove the duplicates from your tree, and I can merge > from it. Now documentation is cleaning. Sorry Yes, I have splitted documentation about USB protocol (into barry/doc) and documentation about JDWP protocol (into barry/bjdwp/doc) If you want keep all documentation into barry/doc ; you can modify (I'll pull again) > Also, there were some chmod permissions that were incorrect for the > java sample (which can mess up CVS), and there were some Sun-copyrighted > documentation files under doc/. So instead of merging, I did my own > rebase, removing the copyrighted files and fixing the permissions. > The rest of the changes I did were done as commits on top of your tree, > which you can follow. > > I've spent time today going through the changes to the Barry library itself, > specifically in the build, makefiles, and src/m_jvmdebug.cc. The rest of > the code has not yet been run or analyzed by me. That bjdwp directory > is your domain for now. :-) I have seen your great job. I have all rebased. Then I have added little fix. PacketJVM function is used by BJDWP tool. BJDWP tool is quiet low level, so I need to manipulate USB packet. And that's why I have exported new headers files. It's so easier for me to work out of barry. I have added Close function in m_jvmdebug class. Indeed, BJDWP is a standalone server and so stays connected. But JDB client (or eclipse) can connect or disconnect of server. When, JDB is disconnected, the mobile phone has to continue to run and doesn't stay blocked ! > I added some TODO list items that need to be handled before 0.16 is > released. I've bumped the 0.16 release target to Sept. 10. > > - figure out a solution to the HideSequencePacket issue > - add copyright notices to all source code files > - write autoconf configure scripts and incorporate into > main configure and build system > - add build tests to test/buildtest.sh script > - fix any lingering compile problems and FIXMEs > - man page for bjdwp app > - www documentation for bjdwp app > - add bjdwp to debian and rpm binary packages > > Due to some changes that I reverted in the main library, bjdwp probably won't > compile right now. We'll need to find a solution to this. Into my GIT repository, BJDWP compile. In your GIT repository, you have to comment the call to Close function to compile. (barry/bjdwp/src/server.cc:225) > Thanks for these features! And thanks for moving to git. :-) > I hope all future changes to bjdwp and the library can be done in > small, single-topic commits. Now, the changement into barry library should be minor... I think that I should add only new command (as SimpleCmd / ComplexCmd) and rename the Unknown function if I find the meaning ! But I have still a lot of work to get a bjdwp entirely functional. When BJDWP will be usable, we can modify building tool (cmake => autotools) and export bjdwp binary tool. For the moment, it's experimental and secret :) Regards, -- Nicolas VIVIEN ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
