Independent Developers

@Sachin-Bhatt It's not a problem, you can ask whatever you wish. And sometimes you will get answers if it's not Qt. Just (a) you didn't get any! and (b) I think your question is so specific/detailed that you need/might be better in a specialist, dedicated forum for this one.

@SGaist Thanks for the responses !!!! Your all inputs helped me to bring output as needed in the development.

I have looked at both projects and decided to go the way GPGTooles goes. On a webserver a license can be bought, and I create a license file which is basically a JSON object encrypted with libsodium using a private/public key. This gets decrypted in the actual Qt app. Once it can be decrypted and the data in the JSON is valid the app can be used. Thanks for the hints.

Hi, That's a Qt forum so not really suited for deep learning related questions. You should rather check a dedicated forum. That said, you should check your preprocessing steps to ensure your data are properly prepared.

@MUYUN The license is actually mentioned, at least in this header file: https://codebrowser.dev/qt5/qtbase/src/platformheaders/xcbfunctions/qxcbwindowfunctions.h.html

@Sachin-Bhatt My explanation: True evaluates to 1 in a numerical context. False evaluates to 0. So: True +3 = 4 1 + 4 = 5 2 + False = 2

@CollinK80 said in Qt 6.2 'QtAndroid file not found error #include <QtAndroid> is not working....: you need to edit CMakeLists.txt to tell it you want the AndroidExtras package Well, this is how things work: if you need something you need to tell CMake that you need it, there is no magic. I don't see what is "ridiculous" about it.

@Olivier92m Hi! You should ask this QtCompany directly. It also depends what license you want to use and how (open source/commercial, are you going to change Qt code or not).

@Lucky01 So far you have asked about Laravel and SQL in PHP. Why do you want to use this forum if you are using them and not Qt? Beats me.

@Paul-Colby thanks this is really helpful

Good news about this is that Qt has a nice balance in its bank account and these guys can make Qt better more quickly.

@SGaist Thank you very much for updating me.

@J-Hilk Thanks for info. I try to create a "Hello word" with external storage.

@jeremy_k Alright! d) says that if you provide your software as a download, then the download of the source (Qt's source in this specific case) can be hosted somewhere else. Good to know! b) is the case with the written offer. But a) is the most relevant: It says that if you ship the object code (i.e. the application) in a physical product (and I would count an embedded device to be such a product) you need to ship the source code on a physical medium as well. Thus, download only wont cut it. Where I was mistaken in the details is that the physical medium does not have to be the same. But it has to be a "durable physical medium customarily used for software interchange". So, this means the Qt source does not have to be on the embedded device itself (or rather can't be as it is not "customarily used for software interchange"). A CD or DVD would certainly work. I would hope that a USB thumb drive or an SD card would to the trick as well.

@SGaist when i try to use the bellow command ninja && ninja install ld: error: relocation R_X86_64_PC32 cannot be used against symbol TT_RunIns; recompile with -fPIC defined in /usr/local/lib/libfreetype.a(truetype.o) referenced by truetype.c truetype.o:(tt_size_init_bytecode) in archive /usr/local/lib/libfreetype.a clang++: error: linker command failed with exit code 1 (use -v to see invocation) readelf -h libfreetype.a | grep 'Class|File|Machine' File: libfreetype.a(ftsystem.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftdebug.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftinit.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftbase.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftbbox.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftbdf.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftbitmap.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftcid.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftfstype.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftgasp.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftglyph.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftgxval.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftmm.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftotval.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftpatent.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftpfr.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftstroke.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftsynth.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(fttype1.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftwinfnt.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(truetype.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(type1.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(cff.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(type1cid.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(pfr.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(type42.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(winfnt.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(pcf.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(bdf.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(sfnt.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(autofit.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(pshinter.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(raster.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(smooth.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftcache.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftgzip.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftlzw.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(ftbzip2.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(psaux.o) Class: ELF64 Machine: Advanced Micro Devices X86-64 File: libfreetype.a(psnames.o) Class: ELF64 Machine: Advanced Micro Devices X86-64

@jsulm sir, thank you very much....

Hi, and welcome! @guplasse said in Qt for commercial Use: If i build my sofware with QT Open Source Licence, can i sell it ? Yes, you can. if yes what are the conditions ? These are specified by the license. (Note: Some Qt modules are available under both the LGPL and GPL licenses; other modules are only available under the GPL license) How should I mention that I am using QT ? 2 good places are: In your software's documentation In an "About" dialog that is popped up by the GUI. (This is often placed under the "Help" menu) if i have to buy QT, can i really do whatever i want with the source code ? Yes, you can.

Hi and welcome to devnet, Right from the commit that removed it: Remove "fallback session management" With the Qt6 compatibility break, it can finally be removed. Closing windows (which might quit the application with quitOnLastWindowClosed() true, the default) acted contrary to the documentation of the commitDataRequest() signal, which could have been a hint. This removes the workaround API from the fix for QTBUG-49667 and also removes the problematic feature that it worked around.