That subject almost sounded ironic to me... :) Are you tired of
new changes?
Anyway, nice that this capi finally is developed. I will be back
with some additions to this later. I have written some c-applications
using a mounted fuse filesystem, and I have always been missing lots of
functions and
/*
$Id: owcapi.h,v 1.3 2005/10/11 21:37:21 alfille Exp $
OWFS (owfs, owhttpd, owserver, owperl, owtcl, owphp, owpython, owcapi)
one-wire file system and related programs
By Paul H Alfille
{c} 2003-5 GPL
[EMAIL PROTECTED]
*/
/* OWCAPI - specific header */
/* OWCAPI is the simple
On Wed, 2005-10-12 at 13:17 -0400, Alfille, Paul H.,M.D. wrote:
> Concering "Multiple OW handles"
>
> I don't think the library, owlib, is set up for multiple invokation. All the
> global variables would colide.
>
> Let's see, that includes the input-device and output device chain heads
> (in_con
Concering "Multiple OW handles"
I don't think the library, owlib, is set up for multiple invokation. All the
global variables would colide.
Let's see, that includes the input-device and output device chain heads
(in_connection and out_connection), all the statistics, the cache heads, the
Device a
On Wed, 2005-10-12 at 08:17 +, Sven Geggus wrote:
> I would propose some kind of filehandle for the above functions and the swig
> Interface which would permit us using more than one bus from a given
> program.
I don't know how straightforward this is.
> I think this could look like this (for
On Tue, 2005-10-11 at 21:29 -0400, Paul Alfille wrote:
> > > int OW_get( const char * path, char * buffer, int buffer_length ) ;
> >
> > Don't let the programmer specify a buffer length for gets. It's prone to
> > programming errors. The extra malloc() isn't going to cause any real
> > problems, bu
I have seen this too when cross-compiling rrdtools-1.0.50 to the WRT54G
router. I had to set an environment variable before building the
libraries just to add ".so" as the correct library-extension.
for bash:
> shrext_cmds=".so"
> export shrext_cmds
> ./configure
> make
for tcsh:
> setenv shrex
Thanks a lot for this hint...
Sorry for not doing anything about it until now, but I have been
abroad for a week and came home yesterday evening.
I have updated the configure-script to include those parameters
automatically if host_os is something like *darwin*.
I guess Ross should be able to s
Paul Alfille <[EMAIL PROTECTED]> wrote:
> Very simple library:
> int OW_init( const char * device ) ;
> int OW_get( const char * path, char * buffer, int buffer_length ) ;
> int OW_put( const char * path, const char * buffer, int buffer_length ) ;
> void OW_finish( void ) ;
>
> Seems to work.
Ni
