MacOS build problems. Developers with MacOS machine wanted.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

MacOS build problems. Developers with MacOS machine wanted.

Jan Kandziora
Hi,

as noted in trouble ticket #70

https://sourceforge.net/p/owfs/mailman/message/30219156/

is still there. Is there any owfs developer with access to a MacOS
machine who can fix this?

Kind regards

        Jan


------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
Reply | Threaded
Open this post in threaded view
|

Re: MacOS build problems. Developers with MacOS machine wanted.

Stefano Miccoli
Just for info:

swig+php is broken also on raspberrypi and Arch Linux.

The compilation of ow_wrap.c miserably fails with tens of errors and uncountable warnings. My current configuration is

$ lsb_release -a
LSB Version: 1.4
Distributor ID: Arch
Description: Arch Linux
Release: rolling
Codename: n/a
$ pacman -Q swig php
swig 3.0.10-1
php 7.0.9-1
$ git describe --tags
v3.1p3

I don’t know who is to blame (owfs, swig, or php) and frankly I do not care. In my opinion owfs is relatively easy to setup and configure if you go the right path:
  • installation of owserver alone   
  • configuration and testing with owshell, 
  • scripting with a native owserver client, 
(Here by native I mean without binary dependencies on libow, libowcapi, libownet.)

The problem is that a new user faces too many choices (should I install owhttp? or may be better fuse? swig language bindings, or ownet?) 

Suppose that you are going to access owfs data in python. You can
  1. directly access the bus with OW.py (swig bindings)
  2. access an owserver with OW (swig bindings)
  3. access an owserver with ownet (native client)
  4. have FUSE + filesystem access in python (no client)
  5. have owserver + FUSE + filesystem access
  6. … write here your choice that I failed to mention

It took me a long time to sort things out, just to learn that owfs python building system is broken with respect to modern standards. (In python you should use virtual environments and pypi packages, and not have 'make install' clutter your system-wide python installation.) You know, I ended up writing my own python owserver client implementation, but I feel that new users could be spared this hassle by simply disabling by default in the owfs distribution most of current modules, which are useful only in edge situations.

Stefano




On 08 Aug 2016, at 14:56, Jan Kandziora <[hidden email]> wrote:

Hi,

as noted in trouble ticket #70

https://sourceforge.net/p/owfs/mailman/message/30219156/

is still there. Is there any owfs developer with access to a MacOS
machine who can fix this?

Kind regards

Jan


------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. http://sdm.link/zohodev2dev
_______________________________________________
Owfs-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/owfs-developers