On Thu, Sep 10, 2009 at 02:20:17PM +0200, Nicolas wrote: > I have patched Barry to export endian.h and config.h. > > Look : da7461c9d7b6d8549a23a873c33a9ac473371b82 (endian.h and config.h > added) > And : e0f02d80bc5b57d83e7f51b0fe3b9f1ad27782ac (endian.h and config.h > removed) > > So, I have the same building issue :)
Yes... those impediments are there for a reason. :-) I'm working on moving the low level protocol stuff into the library itself. We shouldn't be afraid of this... that's the library's purpose: to hide all the platform-specific stuff so that the application doesn't have to worry about it, and can rely on a stable API. > bjdwp is linked to 3 libraries : > - libbarry : so I need to know barry configuration. libbarry contains JVM > USB protocol. The JVM USB protocol needs to be in libbarry. I'm working on moving that now. > - libbarry-jdwp : contains JDWP TCP/IP protocol Ok. > - libbarry-debug : this lib is the ".debug" parser. Ok. I'm starting to wonder if these libraries should just be in the main src directory, and create the libraries using the existing autoconf. Which should be easy to do. I'll see how far I get. > bjdwp contains only a "main" function. Excellent. :-) > I have all written in libbarry-jdwp ; because I'm intend to write a gbjdwp > application (GUI frontend for bjdwp) Sounds good to me. > I have also written all into library, so as to you can easily integrate > some parts into libbarry. We'll see how easily it goes. :-) Thanks, - Chris ------------------------------------------------------------------------------ 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
