Re: [Owfs-developers] Re: running on Mac OS X

Thu, 13 Oct 2005 18:00:25 -0700

Thanks Christian & Scott,

The latest CVS appears to compile OK using gcc 3.3 & 4.0, and I am happy to say it starts up with the following:

./owhttpd -p 3001 -u --error_level=4
INFO: PARSENAME path=
ERR: Opened USB DS9490 adapter at 003/004-04fa-2490-ff-ff.
: Unknown error: 0
INFO: DS9490_setup_adapter: done
INFO: DS9490_overdrive()
INFO: DS9490_reset: ok
INFO: Found device [207EE80000000080] on adapter [003/004-04fa-249207EE80000000080]
INFO: DS9490_reset: ok
INFO: Found device [10E41A140008008F] on adapter [003/004-04fa-24910E41A140008008F]
INFO: DS9490_reset: ok
INFO: Found a DS1420 device [818DE12400000063]
INFO: Found device [818DE12400000063] on adapter [003/004-04fa-249818DE12400000063]
INFO: Set DS9490 [818DE12400000063] unique id to adapter [003/004-04fa-249818DE12400000063]

These family and id codes seem to match what I've seen in OneWireViewer with the exception of not finding a DS2423 chip.

The souceforge page says "The program should be rather self-explanatory" so this is what I tried,  correct me if I'm doing it wrong.  In a web browser pointed to http://localhost:3001/   I get a directory page with links to 7 directories.  Selecting /structure//10 all the fields (ie address, family, ect.) contain "a,000000,000001,ro,000016," or something similar, with the temperature, temphigh, templow fields empty.  Other /structure/family code pages look basically the same.  A url of http://localhost:3001/10.E41A14000800.8F/temperature returns a Non-existent Device page.

If there are any logs to look at or test to try please let me know.
Ross

On Oct 12, 2005, at 5:19 AM, Christian Magnusson wrote:


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 start owserver and owhttpd on
MacOS X now at least...  It seems to be possible to add support
owperl and the other swig extensions later, but could we confirm
that the first binaries are compiling and are usable first...


Check out the latest cvs, and:
./bootstrap
./configure --disable-swig
make


/Christian


On Wed, 2005-10-05 at 21:33 +0000, Scott Hughes wrote:

Ross Cathriner <rnc <at> mac.com> writes:


Another big step forward, maybe.  This version passed all the way  
thru make install.  The following error occurs when executing a  
command:  ./owhttpd -V  or ./owserver -V
dyld: Symbol not found: _kCFRunLoopDefaultMode
   Referenced from: /usr/local/lib/libusb-0.1.4.dylib
   Expected in: flat namespace
Trace/BPT trap



To fix this "symbol not found", you need to tell GCC to reference the
appropriate OS X frameworks.  I really wish this happened in a more 
automagical way with GCC...  Just add the following switches to the 
final (linking) GCC command:

-framework IOKit -framework CoreFoundation

I'm looking forward to trying out owhttpd again soon, now that I see
there is a workaround for the swig problems.

Scott
--
Scott Hughes





-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
_______________________________________________
Owfs-developers mailing list




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
_______________________________________________
Owfs-developers mailing list


Reply via email to