The Grijjy team is proud to introduce our GrijjyCloudLogger

The Grijjy team is proud to introduce our GrijjyCloudLogger,
https://blog.grijjy.com/2017/08/22/grijjycloudlogger-remote-logging-for-windows-ios-android-macos-and-linux/

Cross-platform remote logging with numerous features including custom live watches, live views of Delphi objects remotely, tracking memory usage, object allocations, growth leaks and more.
https://blog.grijjy.com/2017/08/22/grijjycloudlogger-remote-logging-for-windows-ios-android-macos-and-linux/

Comments

  1. Scott Pinkham Yes indeed, this is most likely caused by missing the zmq library. On Linux, macOS and Windows you need to deploy or copy the ZeroMQ library with your app. You can use the Delphi Deployment Manager to do this for the log client apps. In the case of the Broker on Linux you just copy the libzmq-linux64.so that is located in our ZeroMQ library, github.com - DelphiZeroMQ to the same folder where the Broker is located. I updated the Broker so it will output a verbose error in the console, instead of only throwing a runtime error. You also need the other required libraries for Linux as Embarcadero advises, such as build-essential.

    ReplyDelete
  2. Allen Drennan I'm really impressed with the quality of the code and your support, especially considering the price (free!!!). I do still get a runtime error 217, saying that I need to deploy the libzmg-linux46.so, but I did copy it to the same folder as the broker, and gave it full rwx permissions. I haven't installed the build-essential dependencies yet, so I'll try that next. Update: Installing the build-essentials package resolved the error, so the broker is now running on my linux VM on Azure!

    ReplyDelete
  3. Scott Pinkham Glad you got it working on Linux Azure! I also prefer Linux cloud boxes instead of Windows, cheaper too.

    ReplyDelete

Post a Comment