Am 05.02.2016 um 10:36 schrieb Stefano Miccoli:
>
> In your config the perl/python/php/tcl language binding are not
> available due to the lack of swig. If you brew-install swig you
> should unlock the perl/python/php/tcl bindings.
>
The tcl binding is not built on top of SWIG and there is no o
> On 05 Feb 2016, at 07:36, Dean Waldow wrote:
>
> $ brew install pkg-config
>
Sorry my fault: I have a bunch of brew packages installed and was not able to
track down all dependencies…: I read the thread to late to give advice.
Just a few comments.
Fuse is really not necessary: it is hand
Success!
> When I have access to my 1-wire hardware I’ll give it a try.
I was able to test the install and it worked well! I was able to see (owdir)
and read (owread) all of the devices I have from Hobby Boards: Temp,
Temp/Humidity, hub, and a moisture meter using the owserver. I’ll have to pl
Quick update.
I thought I would retry the ./configure again and it FOUND libusb now and it is
enabled. I am confused though because pkg-config still doesn’t find libusb but
it succeeds?
$ pkg-config libusb --cflags
Package libusb was not found in the pkg-config search path.
Perhaps you should
Hi Jan,
> It uses pkg-config.
>
> $ pkg-config --exists libusb-1.0 && echo "libusb-1.0 exists!"
>
>
>> /usr/local/lib/libusb-0.1.4.4.4.dylib /usr/local/lib/libusbdll.dylib
>>
> That's libusb0.
>
>
>> /usr/local/lib/libusbpp-0.1.4.4.4.dylib
>> /usr/local/lib/libusbpp-0.1.4.dylib /usr/local/
Hi Folks,
> at least the current master (or well, ftdi branch but nothing touched there
> since 9a8aa0 == 3.1p1) detects libusb properly on my OS X (10.10.5):
I was using simply the 3.1p1 on OS X 10.11.3 on a pretty old iMac.
> checking for LIBUSB... yes
> ...
> Compile-time options:
>
Hi,
at least the current master (or well, ftdi branch but nothing touched
there since 9a8aa0 == 3.1p1) detects libusb properly on my OS X (10.10.5):
checking for LIBUSB... yes
...
Compile-time options:
USB is enabled
I have no custom configure flags, and libusb from brew
Am 04.02.2016 um 22:28 schrieb Dean Waldow:
>
> checking for LIBUSB... no
>
> I have not dug into the code to see where it is looking for libusb. I
> seem to remember that in MacPorts there were two libusb portions
> (libusb and libusb-development) - doubt there is something similar in
> brew. I o
Hi Jan and Stefano,
I followed Stefano’s information below up to the point of trying to run it with
devices attached. I first removed MacPorts and then installed HomeBrew, wget,
and libusb. I used wget to get owfs-3.1p1.
$ brew install libusb
$ tar xvzf owfs-3.1p1.tar.gz
$ cd owfs-3.1p1
$ ./con
Here is my recipe that worked with yosemite+homebrew
$ brew install libusb
$ tar xvzf owfs-3.1p1.tar.gz
$ cd owfs-3.1p1
$ ./configure --prefix $HOME/owfs-install --disable-owtcl
$ make -j4
$ make install
$ $HOME/owfs-install/bin/owserver -u -—foreground
from another terminal:
$ $HOME/owfs-instal
Am 03.02.2016 um 19:59 schrieb Dean Waldow:
>
> I don’t think libusb-1.0 is standard in el capitan but I believe
> MacPorts has that in their ports. The main issue may be the location
> of the libs from MacPorts versus the where owfs expects to find
> them?
>
./configure looks at all places where
Thanks Jan!
>> I am curious if owfs should be able to be installed on OSX? It seems
>> that it is intended to be installed on OSX from what I have read
>> onine perhaps with the exception of the fuse file system.
>>
> Besides owfs and core owlib, all programs use plain TCP sockets, so they
> sho
Am 03.02.2016 um 18:36 schrieb Dean Waldow:
>
> I am curious if owfs should be able to be installed on OSX? It seems
> that it is intended to be installed on OSX from what I have read
> onine perhaps with the exception of the fuse file system.
>
Besides owfs and core owlib, all programs use plain
Greetings,
I hope this is not too much of a newbie question and this list may be more
focused on development only...
I have used owfs in the past on redhat and centos but would really like to put
owfs on an OSX box. About a month ago, I spent a fair bit of time trying to
compile / install ow
Ahh yes. getline is a GNU extension and not available in all
libraries. I put in a compatible implementation for other platforms
that seems to work well.
Paul
On Thu, Mar 25, 2010 at 4:23 AM, Peter Radcliffe wrote:
> Paul Alfille probably said:
>>Great work, I'll try to address the issues you b
Paul Alfille probably said:
>Great work, I'll try to address the issues you brought up:
Thanks.
>3. Can you give more information about the owhttpd problem? There are
>no unusual dependencies as far as I know -- should be straight C code.
>Perhaps some issue with thread or signal handling?
With
Great work, I'll try to address the issues you brought up:
1. I added your writeup to the website. http://owfs.org/index.php?page=macintosh
2. Great news about FUSE. Made the change.
3. Can you give more information about the owhttpd problem? There are
no unusual dependencies as far as I know -- s
I was recently introduced to 1-wire sensors after setting up power
monitoring from a currentcost unit via a usb interface cable to my mac
mini running osx 10.5. I want to use the same machine for 1-wire since
it's the only machine I have at home that is on all the time.
Since I want to use switche
18 matches
Mail list logo
