Enginio Qt library - Release v0.4.0
0.4.0 version from Enginio Qt library is now out.
Changes & additions:
- New UsergroupOperation to manage usergroup members
- Usergroup members can be listed with QueryOperation
- Usergroups for current user are provided from login operation
- Null JSON value handling in EnginioJsonObject
- Default flags usage in ObjectModel
- Internal ACL handling problems
Also Enginio sample apps were migrated to new library version + various improvements and fixes were done to them at the same time.
- Improved samples can be checked by creating new backends based on provided backend templates in "Enginio Dashboard":https://dashboard.engin.io/ and then downloading sample app codes from Dashboard.
- Or by gettings codes directly from "GitHub repositories":https://github.com/enginio and following application specific configuration instructions in their README files.
I have build Qt5.1 beta statically, and wants to use Enginio as my backend. However when I use mingw32-make install, some strange error happens. I don't know what to do next. Please help me out, thanks.
Problem solved because my Qt version is not complete.
However when I build a very very simple test program, It always gets error when the links to the object. MinGW wersion are attached by Qt5.0.2. Here is the snapshot.
Could you try adding to your project file:
CONFIG *= no_smart_library_merge
Also you could probably try one of the new Qt 5.1RC package candidates to see if it is a 5.0.2 issue:
Sorry to bother you again.
Now I have switched to Qt5.1beta "Click here to view detailed information":http://download.qt-project.org/development_releases/qt/5.1/5.1.0-beta1/qt-windows-opensource-5.1.0-beta1-mingw47_opengl-x86-offline.exe and used MinGW inside it as my default compiler and linker.
At the same time, I tried to compile Qt5.1.0 beta from its source. I tried -openssl-linked OPENSSL_PATH="C:/OpenSSL-Win32" OPENSSL_LIBS="-lssleay32 -llibeay32" switch to integrate OpenSSL into binaries.
However when I build a simple program the problem remains the same. I wonder if it is not compatible with Qt5.1beta static. please help.
!http://i1288.photobucket.com/albums/b485/jiangcaiyang/44_zps11f11a1a.png(The same link error)!
The second question is when I build Enginio with Qt5.1.0beta, and run a simple program, the build procedure goes well with no compile and link error. but when I try pushing my EnginioJsonObject into backend, unexpected sentences pops up. the sentence reads:
I wonder if I use a backend early created when Enginio v0.2.1 came out. But after I create a new backend and exchanges backend ID and secret code into new one, The problem remains the same.
Maybe it is difficult for you to read all through this words, I really wants to get it work, because Enginio is a great cloud solution for Qt developers.
Note that Enginio is still in technical preview state, the output you see are not error but debug messages. Those should be removed with the next release.
For the build issue, it seems to be some export problem on Windows when you build statically, we will look into it.