[Interest] Date Time issue
Roland Hughes
roland at logikalsolutions.com
Fri Oct 5 21:29:43 CEST 2018
>Am unable to set date and time(beyond 2038) using QDateTime on 32 bit linux
kernel. Using QDateTime::currentdatetime() to retrieve the current
datetime set.
>Please let me know if there is any API to set date and time or do I need to
upgrade to 64 bit linux kernel to resolve the same?
http://neilrieck.net/docs/calendar_time_y2k_etc.html
click on the Y2038 link
---
Roland Hughes, President
Logikal Solutions
(630)-205-1593 - cell
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.johnsmith-book.com
http://www.logikalblog.com
On 2018-10-05 12:49, interest-request at qt-project.org wrote:
> Send Interest mailing list submissions to
> interest at qt-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.qt-project.org/mailman/listinfo/interest
> or, via email, send a message with subject or body 'help' to
> interest-request at qt-project.org
>
> You can reach the person managing the list at
> interest-owner at qt-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Interest digest..."
>
> Today's Topics:
>
> 1. Re: QML id as string? (Jason H)
> 2. Including Qt Quick 2 extension plugin in Android App (Ren? Hansen)
> 3. Re: Including Qt Quick 2 extension plugin in Android App
> (J?r?me Godbout)
> 4. Qt, iOS, CoreNFC? (Jason H)
> 5. Re: Including Qt Quick 2 extension plugin in Android App
> (Ren? Hansen)
> 6. QDatetime issue with date beyond 2038 (Ramakanth Kesireddy)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 4 Oct 2018 17:06:51 +0200
> From: "Jason H" <jhihn at gmx.com>
> To: "Jason H" <jhihn at gmx.com>
> Cc: "J?r?me Godbout" <godboutj at amotus.ca>, "Qt Interest"
> <interest at qt-project.org>
> Subject: Re: [Interest] QML id as string?
> Message-ID:
> <trinity-360786f2-b52d-4f0b-a838-5f51288c49a8-1538665611065 at 3c-app-mailcom-bs10>
>
> Content-Type: text/plain; charset="us-ascii"
>
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181004/2a8ddec1/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 4 Oct 2018 22:38:41 +0200
> From: Ren? Hansen <renehh at gmail.com>
> To: interest <interest at qt-project.org>
> Subject: [Interest] Including Qt Quick 2 extension plugin in Android
> App
> Message-ID:
> <CAB-60njDk7nuTFffDrAYAc1+dc0J+kkTcnAZs+GVWbSXewi7FQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi everyone,
>
> I can't seem to get the voodoo right on something that should be trivial.
>
> My use case is this; I have two Android apps, which uses similar logic that
> I'd like to extract and share between them, in the form of an extension
> plugin. Easy peasy right? Well, I just can't seem to figure it out.
>
> In order to distill my understanding of how this is supposed to work I've
> created a simple example in this repo:
>
> https://github.com/rhardih/app-with-extension-example
>
> All I've done is the following:
>
> 1. Generated the default Qt Quick Controls 2 Swipe app.
> 2. Generated the default Qt Quick 2 extension plugin.
> 3. Added a custom QML invokable method, "foo()" on the default "MyItem".
> 4. Updated the App.pro file, and specified the extension's install path,
> (Maybe incorrectly), to the QML_IMPORT_PATH
>
> I get the autocompletion inside QtCreator for "MyItem" and no import errors
> in the editor, so something must be right.
>
> However... as soon as I run the App, i get:
>
> W libApp.so: (null):0 ((null)): QQmlApplicationEngine failed to load
> component
> W libApp.so: (null):0 ((null)): qrc:/main.qml:4 module
> "com.mycompany.qmlcomponents" is not installed
>
> The extension build folder looks like this after a build:
>
> ??? Makefile
> ??? android-build
> ? ??? Users
> ? ? ??? rene
> ? ? ??? Code
> ? ? ??? Qt
> ? ? ??? 5.11.1
> ? ? ??? android_armv7
> ? ? ??? qml
> ? ? ??? com
> ? ? ??? mycompany
> ? ? ??? qmlcomponents
> ? ? ??? qmldir
> ? ??? libs
> ? ??? armeabi-v7a
> ? ??? libExtension.so
> ??? extension_plugin.o
> ??? libExtension.so
> ??? moc_extension_plugin.cpp
> ??? moc_extension_plugin.o
> ??? moc_myitem.cpp
> ??? moc_myitem.o
> ??? moc_predefs.h
> ??? myitem.o
> ??? qmldir
>
> Even so, libExtension.so isn't included in the .apk after building the app.
> I can get it included by adding ANDROID_EXTRA_LIBS += <path
> to>/libs/armeabi-v7a/libExtension.so, to App.pro, but that doesn't change
> the above error.
>
> I've tried pointing ANDROID_EXTRA_PLUGINS to various locations of the
> extension's install folder as well, but that just seems to dump everything
> underneath the specified path, directly into assets...
>
> Can anyone tell me, how on earth is this supposed to work? Am I just using
> the wrong paths, or am I missing something fundamental here?
>
> /Ren? Hansen
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181004/d2b3dd74/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 4 Oct 2018 17:37:43 -0400
> From: J?r?me Godbout <godboutj at amotus.ca>
> To: renehh at gmail.com
> Cc: Qt Interest <interest at qt-project.org>
> Subject: Re: [Interest] Including Qt Quick 2 extension plugin in
> Android App
> Message-ID:
> <CAAV3L-_RbVDFL3im64n_jAeAvudCNYnrgj_VS+9=5yWMooiQ+A at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Not sure if it might help, but I had some problems with bundling some lib
> with my application and I end up with this in my project:
> android/lib // for my .so library, note the lib without s here
> android/libs // for my .jar library
>
> Then I add those lib into the extra libs into my .pro:
>
> ANDROID_EXTRA_LIBS += \
>
> $$PWD/android/lib/libcrypto.so \
>
> $$PWD/android/lib/libssl.so
>
> Seem like the android/libs folder is somehow special for qmake.
>
> I also attached the copy android sources, if you every need to have
> .pri that want to include android lib on his own,
>
> this is a work derivated from Luke Vear which I talk to on slack when
> I was trying to achieve this.
>
> Including Android lib and .jars from multiple .pri is a huge pain,
> avoid it unless you want to use something like the attached files.
>
> How to use the atatched file:
>
> include(CopyAndroidSources.pri)
>
> defineReplace(androidPathMaker) {
>
> for(a, $$3) {
>
> result += $$1/$$2/$${a}
>
> }
>
> return($$result)
>
> }
>
> defineReplace(androidSourceMaker) {
>
> return($$copyAndroidSources($$1, $$2, $$androidPathMaker($$3,
> $$4, $$5)))
>
> }
>
> SOURCES_ANDROID_WORKPAD_TECHKNOWSERV = \
>
> UhfReader.java
>
> QMAKE_EXTRA_TARGETS +=
> $$androidSourceMaker("WorkpadTechKnowServ_Android_Sources",
> "src/com/amotus/workpad/techknowserv", $$clean_path($$PWD),
> "android-src/src/com/amotus/workpad/techknowserv",
> SOURCES_ANDROID_WORKPAD_TECHKNOWSERV)
>
> LIB_ANDROID_WORKPAD_TECHKNOWSERV = \
>
> libpda.so \
>
> QMAKE_EXTRA_TARGETS +=
> $$androidSourceMaker("WorkpadTechKnowServ_Android_Lib", "lib",
> $$clean_path($$PWD), "android-src/lib",
> LIB_ANDROID_WORKPAD_TECHKNOWSERV)
>
> ANDROID_EXTRA_LIBS += \
>
> $$clean_path($$PWD)/android/lib/libpda.so \
>
> SO you place everything into android-src and copy all the stuff into
> android when building the project, so multiple source can declare
> their own lib usage
>
> On Thu, 4 Oct 2018 at 16:39, Ren? Hansen <renehh at gmail.com> wrote:
>
>> Hi everyone,
>>
>> I can't seem to get the voodoo right on something that should be trivial.
>>
>> My use case is this; I have two Android apps, which uses similar logic
>> that I'd like to extract and share between them, in the form of an
>> extension plugin. Easy peasy right? Well, I just can't seem to figure it
>> out.
>>
>> In order to distill my understanding of how this is supposed to work I've
>> created a simple example in this repo:
>>
>> https://github.com/rhardih/app-with-extension-example
>>
>> All I've done is the following:
>>
>> 1. Generated the default Qt Quick Controls 2 Swipe app.
>> 2. Generated the default Qt Quick 2 extension plugin.
>> 3. Added a custom QML invokable method, "foo()" on the default "MyItem".
>> 4. Updated the App.pro file, and specified the extension's install path,
>> (Maybe incorrectly), to the QML_IMPORT_PATH
>>
>> I get the autocompletion inside QtCreator for "MyItem" and no import
>> errors in the editor, so something must be right.
>>
>> However... as soon as I run the App, i get:
>>
>> W libApp.so: (null):0 ((null)): QQmlApplicationEngine failed to load
>> component
>> W libApp.so: (null):0 ((null)): qrc:/main.qml:4 module
>> "com.mycompany.qmlcomponents" is not installed
>>
>> The extension build folder looks like this after a build:
>>
>> ??? Makefile
>> ??? android-build
>> ? ??? Users
>> ? ? ??? rene
>> ? ? ??? Code
>> ? ? ??? Qt
>> ? ? ??? 5.11.1
>> ? ? ??? android_armv7
>> ? ? ??? qml
>> ? ? ??? com
>> ? ? ??? mycompany
>> ? ? ??? qmlcomponents
>> ? ? ??? qmldir
>> ? ??? libs
>> ? ??? armeabi-v7a
>> ? ??? libExtension.so
>> ??? extension_plugin.o
>> ??? libExtension.so
>> ??? moc_extension_plugin.cpp
>> ??? moc_extension_plugin.o
>> ??? moc_myitem.cpp
>> ??? moc_myitem.o
>> ??? moc_predefs.h
>> ??? myitem.o
>> ??? qmldir
>>
>> Even so, libExtension.so isn't included in the .apk after building the
>> app. I can get it included by adding ANDROID_EXTRA_LIBS += <path
>> to>/libs/armeabi-v7a/libExtension.so, to App.pro, but that doesn't change
>> the above error.
>>
>> I've tried pointing ANDROID_EXTRA_PLUGINS to various locations of the
>> extension's install folder as well, but that just seems to dump everything
>> underneath the specified path, directly into assets...
>>
>> Can anyone tell me, how on earth is this supposed to work? Am I just using
>> the wrong paths, or am I missing something fundamental here?
>>
>> /Ren? Hansen
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/interest
>
> --
>
> RAPPROCHEZ LA DISTANCE
>
> *J?r?me Godbout*Senior Software Developer
>
> *p:* +1 (418) 800-1073 ext.:109
>
> *m:* +1 (581) 777-0050
>
> amotus.ca <http://www.amotus-solutions.com/>
> statum-iot.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181004/8f3440c3/attachment-0001.html>
> -------------- next part --------------
> # MIT License
> #
> # Copyright (c) 2018 Luke Vear
> #
> # Permission is hereby granted, free of charge, to any person obtaining a copy
> # of this software and associated documentation files (the "Software"), to deal
> # in the Software without restriction, including without limitation the rights
> # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> # copies of the Software, and to permit persons to whom the Software is
> # furnished to do so, subject to the following conditions:
> #
> # The above copyright notice and this permission notice shall be included in all
> # copies or substantial portions of the Software.
> #
> # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
> # AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> # LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
> # OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> # SOFTWARE.
> #
> #
> # Taken from https://github.com/lukevear/qmakeAndroidSourcesHelper
> # commit e0e47e0d0f1b70bedcc9e31e9f8b217e027d3a54
> #
> # Modification is as follow
> # 2018-06-01 JG remove the .gitignore section, not needed
> # 2018-06-01 JG return with more export
> # 2018-06-01 JG Add FORCE depends for created target
>
> defineReplace(copyAndroidSources) {
> commandAlias = $$1
> targetDirectory = $$2
> sourceFiles = $$3
>
> # Ensure we were provided a valid alias for this command
> isEmpty(commandAlias) {
> error("copyAndroidSources requires a valid command alias as its first argument.")
> }
>
> # Ensure we were provided a valid target directory
> isEmpty(targetDirectory) {
> error("copyAndroidSources requires a valid target directory path as its second argument.")
> }
>
> # Ensure we were provide a valid set of source files
> isEmpty(sourceFiles) {
> error("copyAndroidSources requires a valid set of files as its third argument.")
> }
>
> # Make sure the command is run, TODO godboutj 2018-06-01, this should be depends on used files instead
> $${commandAlias}.depends += FORCE
>
> # Create the target directory
> # Work around problem with Windows that cannot make or on command and syntaxt is not the same with Windows and other *nix system
> contains(QMAKE_HOST.os, Windows) {
> $${commandAlias}.commands += $$escape_expand(\n\t)$(CHK_DIR_EXISTS) $$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory) $(MKDIR) $$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory)
> } else {
> $${commandAlias}.commands += $$escape_expand(\n\t)$(CHK_DIR_EXISTS) $$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory) || $(MKDIR) $$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory)
> }
> # Process each file that we were provided
> for(fileName, sourceFiles) {
> # Copy the file from the source directory to the target directory
> $${commandAlias}.commands += $$escape_expand(\n\t)$(COPY_FILE) $$shell_path($$fileName) $$shell_path($$ANDROID_PACKAGE_SOURCE_DIR/$$targetDirectory/$$basename(fileName))
> }
>
> # We need to make our new command globally available so that qmake can add it to the generated Makefile
> export($${commandAlias}.commands)
> export($${commandAlias}.depends)
>
> # To ensure our command is run before compilation occurs we add our command to the dependency tree of 'first' (creating the tree if required)
> isEmpty(first.depends) {
> first.depends = $(first) $${commandAlias}
> export(first.depends)
> return(first $${commandAlias})
> }
> first.depends += $${commandAlias}
> export(first.depends)
> return($${commandAlias})
> }
>
> ------------------------------
>
> Message: 4
> Date: Thu, 4 Oct 2018 23:46:02 +0200
> From: "Jason H" <jhihn at gmx.com>
> To: "interestqt-project.org" <interest at qt-project.org>
> Subject: [Interest] Qt, iOS, CoreNFC?
> Message-ID:
> <trinity-01b60113-f717-42e3-b391-9db342ca3f94-1538689562858 at 3c-app-mailcom-bs10>
>
> Content-Type: text/plain; charset=UTF-8
>
> I'm trying to hack NFC support into my app, but CoreNFC is not yet supported by Qt.
>
> https://bugreports.qt.io/browse/QTBUG-63253
>
> It seems simple enough though, but I an not good with Objective-C, and all the examples are in Swift.
>
> So here's what I tried:
> 0. Take care of entitlements and such.
> 1. For my QIOSApplication Deleage, it was
> @interface QIOSApplicationDelegate : UIResponder <UIApplicationDelegate>
> changed to:
> @interface QIOSApplicationDelegate : UIResponder <UIApplicationDelegate, NFCNDEFReaderSessionDelegate>
> 2. Add @property (strong, nonatomic) NFCNDEFReaderSession *nfcSession; to the delegate
> 3. Just as a test, in didFinishLaunchingWithOptions, add:
> if (![NFCNDEFReaderSession readingAvailable]) {
> qDebug() << "NFC not available";
> } else {
> qDebug() << "NFC available";
> _nfcSession = [[NFCNDEFReaderSession alloc] initWithDelegate:self queue:nil invalidateAfterFirstRead:NO];
> [_nfcSession beginSession];
> }
> 4. Add the following functions to the app delegate:
> - (void)readerSession:(NFCNDEFReaderSession *)session didDetectNDEFs:( NSArray<NFCNDEFMessage *> *)messages {
> qDebug() << "NFCNDEFReaderSession didDetectNDEFs" << messages;
> NSLog(@"NFCNDEFReaderSession didDetectNDEFs: %@",messages);
> for (NFCNDEFMessage *message in messages) {
> qDebug() << message;
> for (NFCNDEFPayload *payload in message.records) {
> qDebug() << payload;
> }
> }
> }
>
> - (void)readerSession:(NFCNDEFReaderSession *)session didInvalidateWithError:( NSError *)error {
> NSLog(@"Something went wrong: %@",error);
> }
>
> 5. Launch App, present tag to phone (along the top)
> 6. On removal of the tag I get (3 attempts):
> 2018-10-04 17:36:09.291926-0400 testnfc[532:51484] [CoreNFC] 00000002 838b2f80 -[NFCNDEFReaderSession _connectTag:error:]:418 Error Domain=NFCError Code=100 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2818a2970 {Error Domain=nfcd Code=15 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error}}}
> 2018-10-04 17:36:13.579116-0400 testnfc[532:51484] [CoreNFC] 00000002 838b2f80 -[NFCNDEFReaderSession _connectTag:error:]:418 Error Domain=NFCError Code=100 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2818a03c0 {Error Domain=nfcd Code=15 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error}}}
> 2018-10-04 17:36:16.845026-0400 testnfc[532:51377] [CoreNFC] 00000002 838b2f80 -[NFCNDEFReaderSession _connectTag:error:]:418 Error Domain=NFCError Code=100 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error, NSUnderlyingError=0x2818a8bd0 {Error Domain=nfcd Code=15 "Stack Error" UserInfo={NSLocalizedDescription=Stack Error}}}
>
> 7. The tag is valid because another app in the app store was able to get data from it.
>
> I'm really bad with Objective-C, so aside from compile errors, I don't know if what I am doing is right.
> I'm very unsure about that , NFCNDEFReaderSessionDelegate> part.
>
> Many thanks in advance.
>
> ------------------------------
>
> Message: 5
> Date: Fri, 5 Oct 2018 12:57:26 +0200
> From: Ren? Hansen <renehh at gmail.com>
> To: J?r?me Godbout <godboutj at amotus.ca>
> Cc: Qt Interest <interest at qt-project.org>
> Subject: Re: [Interest] Including Qt Quick 2 extension plugin in
> Android App
> Message-ID:
> <CAB-60ngD76UezfpSCm0SsX16bhf3w-D2CL3_o_qWduYW_ASa_Q at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I don't have the problem if I just want a plain shared library, in that
> case just bundling the .so with ANDROID_EXTRA_LIBS works fine.
>
> Isolating code into an extension plugin with both QML components and Qt
> classes and using that in separate apps is my goal.
>
> If anyone has a working example + build and package process somewhere, I'd
> love to see it.
>
> I simply don't get how it's supposed to work. Most SO answers etc. seem to
> point to people giving up and just copying stuff directly into their apps.
> I just can't get myself to believe there isn't a better way to do this.
>
> /Ren?
>
> On Thu, 4 Oct 2018 at 23:37 J?r?me Godbout <godboutj at amotus.ca> wrote:
>
> Not sure if it might help, but I had some problems with bundling some lib
> with my application and I end up with this in my project:
> android/lib // for my .so library, note the lib without s here
> android/libs // for my .jar library
>
> Then I add those lib into the extra libs into my .pro:
>
> ANDROID_EXTRA_LIBS += \
>
> $$PWD/android/lib/libcrypto.so \
>
> $$PWD/android/lib/libssl.so
>
> Seem like the android/libs folder is somehow special for qmake.
>
> I also attached the copy android sources, if you every need to have .pri that want to include android lib on his own,
>
> this is a work derivated from Luke Vear which I talk to on slack when I was trying to achieve this.
>
> Including Android lib and .jars from multiple .pri is a huge pain, avoid it unless you want to use something like the attached files.
>
> How to use the atatched file:
>
> include(CopyAndroidSources.pri)
>
> defineReplace(androidPathMaker) {
>
> for(a, $$3) {
>
> result += $$1/$$2/$${a}
>
> }
>
> return($$result)
>
> }
>
> defineReplace(androidSourceMaker) {
>
> return($$copyAndroidSources($$1, $$2, $$androidPathMaker($$3, $$4, $$5)))
>
> }
>
> SOURCES_ANDROID_WORKPAD_TECHKNOWSERV = \
>
> UhfReader.java
>
> QMAKE_EXTRA_TARGETS += $$androidSourceMaker("WorkpadTechKnowServ_Android_Sources", "src/com/amotus/workpad/techknowserv", $$clean_path($$PWD), "android-src/src/com/amotus/workpad/techknowserv", SOURCES_ANDROID_WORKPAD_TECHKNOWSERV)
>
> LIB_ANDROID_WORKPAD_TECHKNOWSERV = \
>
> libpda.so \
>
> QMAKE_EXTRA_TARGETS += $$androidSourceMaker("WorkpadTechKnowServ_Android_Lib", "lib", $$clean_path($$PWD), "android-src/lib", LIB_ANDROID_WORKPAD_TECHKNOWSERV)
>
> ANDROID_EXTRA_LIBS += \
>
> $$clean_path($$PWD)/android/lib/libpda.so \
>
> SO you place everything into android-src and copy all the stuff into android when building the project, so multiple source can declare their own lib usage
>
> On Thu, 4 Oct 2018 at 16:39, Ren? Hansen <renehh at gmail.com> wrote:
>
> Hi everyone,
>
> I can't seem to get the voodoo right on something that should be trivial.
>
> My use case is this; I have two Android apps, which uses similar logic
> that I'd like to extract and share between them, in the form of an
> extension plugin. Easy peasy right? Well, I just can't seem to figure it
> out.
>
> In order to distill my understanding of how this is supposed to work I've
> created a simple example in this repo:
>
> https://github.com/rhardih/app-with-extension-example
>
> All I've done is the following:
>
> 1. Generated the default Qt Quick Controls 2 Swipe app.
> 2. Generated the default Qt Quick 2 extension plugin.
> 3. Added a custom QML invokable method, "foo()" on the default "MyItem".
> 4. Updated the App.pro file, and specified the extension's install path,
> (Maybe incorrectly), to the QML_IMPORT_PATH
>
> I get the autocompletion inside QtCreator for "MyItem" and no import
> errors in the editor, so something must be right.
>
> However... as soon as I run the App, i get:
>
> W libApp.so: (null):0 ((null)): QQmlApplicationEngine failed to load
> component
> W libApp.so: (null):0 ((null)): qrc:/main.qml:4 module
> "com.mycompany.qmlcomponents" is not installed
>
> The extension build folder looks like this after a build:
>
> ??? Makefile
> ??? android-build
> ? ??? Users
> ? ? ??? rene
> ? ? ??? Code
> ? ? ??? Qt
> ? ? ??? 5.11.1
> ? ? ??? android_armv7
> ? ? ??? qml
> ? ? ??? com
> ? ? ??? mycompany
> ? ? ??? qmlcomponents
> ? ? ??? qmldir
> ? ??? libs
> ? ??? armeabi-v7a
> ? ??? libExtension.so
> ??? extension_plugin.o
> ??? libExtension.so
> ??? moc_extension_plugin.cpp
> ??? moc_extension_plugin.o
> ??? moc_myitem.cpp
> ??? moc_myitem.o
> ??? moc_predefs.h
> ??? myitem.o
> ??? qmldir
>
> Even so, libExtension.so isn't included in the .apk after building the
> app. I can get it included by adding ANDROID_EXTRA_LIBS += <path
> to>/libs/armeabi-v7a/libExtension.so, to App.pro, but that doesn't change
> the above error.
>
> I've tried pointing ANDROID_EXTRA_PLUGINS to various locations of the
> extension's install folder as well, but that just seems to dump everything
> underneath the specified path, directly into assets...
>
> Can anyone tell me, how on earth is this supposed to work? Am I just
> using the wrong paths, or am I missing something fundamental here?
>
> /Ren? Hansen
>
> _______________________________________________ Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
> --
>
> RAPPROCHEZ LA DISTANCE
>
> *J?r?me Godbout*Senior Software Developer
>
> *p:* +1 (418) 800-1073 <(418)%20800-1073> ext.:109
>
> *m:* +1 (581) 777-0050 <(581)%20777-0050>
>
> amotus.ca <http://www.amotus-solutions.com/>
> statum-iot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.qt-project.org/pipermail/interest/attachments/20181005/f265431e/attachment-0001.html>
------------------------------
Message: 6
Date: Fri, 5 Oct 2018 23:18:18 +0530
From: Ramakanth Kesireddy <rama.kesi at gmail.com>
To: interest at qt-project.org
Subject: [Interest] QDatetime issue with date beyond 2038
Message-ID:
<CAFi1RNiRW2eAOPEAXT17gp1CRsghKYEJi9yJX0AGdwLLgQjW5w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Am unable to set date and time(beyond 2038) using QDateTime on 32 bit
linux
kernel. Using QDateTime::currentdatetime() to retrieve the current
datetime set.
Please let me know if there is any API to set date and time or do I need
to
upgrade to 64 bit linux kernel to resolve the same?
Best Regards,
Ramakanth
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.qt-project.org/pipermail/interest/attachments/20181005/d412995c/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
------------------------------
End of Interest Digest, Vol 85, Issue 6
***************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20181005/7f8d0514/attachment.html>
More information about the Interest
mailing list