Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ohNet Installtion
05-02-2013, 11:20 AM
Post: #9
RE: ohNet Installtion
Hi Steve,

I can probably help you with building ohOS, but I should first say that our focus is currently more toward the AV aspects of Openhome, and we're anticipating making some significant changes to ohOS before it's a particularly stable platform to develop against.

May I ask what you hope to do with ohOS? While we have worked on a home automation app based on ohOS, we have not yet released it. ohOS on its own provides some package management and networking services to home applications. You're welcome to use it for hosting your own applications, but be aware that ohOS itself doesn't have a stable API yet, so you may well need to make significant changes to such applications when the ohOs API is revised.

The ohdevtools version message is an indicator that recent versions of ohdevtools made backwards-incompatible changes. Looking at it, it appears that ohOS was not affected by those changes, so I'll update the version number it's looking for. In the mean-time, you can do the same by editing "projectdata/build_behaviour.py". The required version number appears near the top. We try to avoid making backwards-incompatible changes to ohdevtools, since it (by necessity) lives outside our dependency-fetching system, but sometimes it's necessary.

I'm surprised that ./go fetch is failing to fetch Moq. It works for me on my Windows-x86 machine. I see output like this:

Code:
Performing step 'choose_optional_steps' (reason: 'required')
Performing step 'choose_platform' (reason: 'required')
Performing step 'setup_universal' (reason: 'required')
Performing step 'setup_windows' (reason: 'required')
Performing step 'setup_windows_x86' (reason: 'required')
Performing step 'fetch' (reason: 'default')
Fetching 'Firefly'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/Firefly.0.4+openhome.1.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Fetching 'ndesk-options'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/ndesk-options-0.2.1.bin.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Fetching 'ohNet'
  from 'http://openhome.org/releases/artifacts/ohNet/ohNet-1.0.362-Windows-x86-dev-release.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\Windows-x86'
  OK
Fetching 'Renci.SshNet'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/Renci.SshNet-14316.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Fetching 'NuGet'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/NuGet.1.7.30402.9028.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Fetching 'yui-compressor'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/yui-compressor.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Fetching 'SharpZipLib'
  from 'http://openhome.org/releases/artifacts/AnyPlatform/SharpZipLib_0840_Bin.tar.gz' (web)
  unpacking to 'W:\git\ohos\dependencies\AnyPlatform'
  OK
Successfully installed 'Gate 0.3.6'.
Successfully installed 'Gate.Hosts.Firefly 0.3.6'.
Successfully installed 'Kayak 0.7.2'.
Successfully installed 'Moq 4.0.10827'.
Successfully installed 'NUnit 2.6.0.12054'.
Successfully installed 'NUnit.Runners 2.6.0.12051'.
Successfully installed 'Owin 0.7'.
Successfully installed 'log4net 2.0.0'.
Performing step 'configure' (reason: 'default')
...

Gate, Kayak, Moq, NUnit, Owin and log4net are fetched using NuGet. I think the note in the README about "--moq-dir" is a little bit dated. If you run "./waf --help" you'll see that there is an option called "--nuget-moq-dir".

We have found NuGet to be quite flakey under Mono, particularly prior to Mono 3.0. Did it fetch the other dependencies correctly? What error message did you see for Moq?

I note that you're developing on a Raspberry Pi with the armhf architecture. You should be okay so long as ohNet and Mono work well on that platform, since every other dependency is platform-independent, but we don't have any such systems that we test on.

You don't need to "make install" ohNet to use it with ohOS. At present, ohOS just treats it as another private library and installs a private copy in its own directory.
Visit this user's website Find all posts by this user


Messages In This Thread
ohNet Installtion - steve - 04-02-2013, 04:26 PM
RE: ohNet Installtion - simonc - 04-02-2013, 04:40 PM
RE: ohNet Installtion - steve - 04-02-2013, 04:48 PM
RE: ohNet Installtion - simonc - 04-02-2013, 05:10 PM
RE: ohNet Installtion - steve - 04-02-2013, 05:20 PM
RE: ohNet Installtion - steve - 04-02-2013, 06:42 PM
RE: ohNet Installtion - simonc - 04-02-2013, 08:05 PM
RE: ohNet Installtion - steve - 05-02-2013, 09:15 AM
RE: ohNet Installtion - andreww - 05-02-2013 11:20 AM
RE: ohNet Installtion - steve - 05-02-2013, 11:48 AM
RE: ohNet Installtion - andreww - 05-02-2013, 12:01 PM
RE: ohNet Installtion - steve - 05-02-2013, 12:59 PM
RE: ohNet Installtion - steve - 05-02-2013, 03:43 PM
RE: ohNet Installtion - simonc - 05-02-2013, 04:34 PM
RE: ohNet Installtion - andreww - 05-02-2013, 04:56 PM
RE: ohNet Installtion - steve - 05-02-2013, 05:17 PM
RE: ohNet Installtion - steve - 05-02-2013, 10:09 PM
RE: ohNet Installtion - andreww - 06-02-2013, 09:55 AM
RE: ohNet Installtion - steve - 06-02-2013, 12:09 PM
RE: ohNet Installtion - simonc - 06-02-2013, 12:14 PM
RE: ohNet Installtion - simonc - 06-02-2013, 01:28 PM
RE: ohNet Installtion - steve - 06-02-2013, 12:21 PM
RE: ohNet Installtion - steve - 06-02-2013, 01:48 PM

Forum Jump: