Hi again,
I figured this out with the help of Mr Google :-) It looks like the Ruby gem stuff is a very similar idea to npm for node.js so all I needed to do was to do
sudo gem install rspec
sudo gem install simplecov

and I was back on the saddle again, however I *really* don't think that missing these things should result in a fatal error for the whole cmake, that seems a little bit unfriendly and it didn't used to do this.

Also could someone please explain the reason for the change around the "SYSINSTALL_BINDINGS is unspecified" stuff? Why make the default behaviour do something that "will no longer be found by system interpreters. This means that every user will be required to manually configure their interpreters to locate the proton bindings". Clearly -DSYSINSTALL_BINDINGS=ON will make it behave like it used to do, but why change that from the default? It might be good if the text is modified to say *why* this is no longer the default, 'cause it seems kind of odd.

Cheers,
Frase

On 26/04/14 14:38, Fraser Adams wrote:
Hello,
I've just done an svn update and now cmake .. fails for me :-( the cmake output is copied below, it looks like the main culprit relates to the ruby bindings:
-- Missing Ruby gem dependency: rspec
-- Missing Ruby gem dependency: simplecov

A couple of things:
1. should this really be a fatal error that stops cmake working at all shouldn't it just log that the ruby bindings and things can't be build (in a similar way to PerlLibs Not Found - incidentally I reckon there is a bug in the PerlLibs library finder, 'cause I've certainly got it installed and the CMake for qpid finds it OK). 2. What the heck to the ruby errors mean and how do I fix them? TBH I know absolutely zero about ruby, I've just checked on my Ubuntu package manager though and it is reporting that librspec-ruby 2.5.0-1 is installed and ruby-rspec, ruby-rspec-core, ruby-rspec-mocks and ruby-rspec-expectations and yet cmake still says "Missing Ruby gem dependency: rspec" and I can't see anything related to simplecov in my Ubuntu package manager.

Any thoughts?
Frase


-- The C compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- PN_VERSION: 0.7
CMake Warning at CMakeLists.txt:83 (message):
SYSINSTALL_BINDINGS is unspecified, defaulting it to OFF. Please note that the default install behaviour of proton has changed. Proton bindings by default will now be installed under lib/proton/bindings and will no longer
  be found by system interpreters.  This means that every user will be
  required to manually configure their interpreters to locate the proton
bindings. If you wish proton bindings to be installed into the interpreter specified locations as was the default in prior releases, please specify
  -DSYSINSTALL_BINDINGS=ON


-- Found Java: /usr/lib/jvm/java-6-openjdk/bin/java
-- checking for module 'openssl'
--   found openssl, version 1.0.0e
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libssl.so;/usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1..")
-- Found PythonInterp: /usr/bin/python2.7
-- Looking for clock_gettime
-- Looking for clock_gettime - not found.
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - found
-- Looking for uuid_generate
-- Looking for uuid_generate - not found.
-- Looking for uuid_generate in uuid
-- Looking for uuid_generate in uuid - found
-- Looking for strerror_r
-- Looking for strerror_r - found
-- Looking for atoll
-- Looking for atoll - found
-- Found SWIG: /usr/bin/swig (found version "1.3.40")
-- Found PythonLibs: /usr/lib/libpython2.7.so
-- Found Ruby: /usr/bin/ruby (found version "1.8.7")
-- Missing Ruby gem dependency: rspec
-- Missing Ruby gem dependency: simplecov
-- Found Perl: /usr/bin/perl
-- Trying alternative search for Perl
-- PerlLibs Not Found
CMake Error at proton-c/bindings/ruby/CMakeLists.txt:21 (message):
  Ruby bindings cannot be tested while missing dependencies


-- Configuring incomplete, errors occurred!



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to