Opendds-3.13 Release build failure - qt

I'm making release build of my Application in QT + opendds-3.13 i m getting this error.
..\OpenDDS-3.13\ACE_wrappers\ace/OS_NS_netdb.inl(794): error C2440:
'return': cannot convert from 'WCHAR *' to 'const ACE_TCHAR *'
although i can successfully build the debug version only facing this problem in release build.

Very likely you have incorrect compiler settings, check especially the unicode settings of your project.

Related

Deploy Qt Design Studio Project for Webassembly

I am using Qt 6.3.2 and im on a M1 Mac.
I am trying to build a Qt Design Studio Project for webassembly but I have trouble to install the Designer Components for Webassembly.
To use a Design Studio Project, you have to install the Designer Components to your Installation, which I did like stated in the documentation:Adding Qt Quick Designer Components to Qt Installations.
This works fine when I build it for Mac but I cant get it to work with WASM. Do I need to build the components in a specific way for em++?
When I use the components like stated in the docs I get the following error message:
em++: warning: unrecognized file type: `/Users/marius/Qt/6.3.2/wasm_32/./qml/QtQuick/Studio/Effects/libquickstudioeffectsplugin.dylib`. Mapping to `-lquickstudioeffectsplugin` and hoping for the best [-Wmap-unrecognized-libraries]
em++: warning: unrecognized file type: `/Users/marius/Qt/6.3.2/wasm_32/./qml/QtQuick/Studio/Application/libquickstudioapplicationplugin.dylib`. Mapping to `-lquickstudioapplicationplugin` and hoping for the best [-Wmap-unrecognized-libraries]
em++: warning: unrecognized file type: `/Users/marius/Qt/6.3.2/wasm_32/./qml/QtQuick/Studio/EventSimulator/libquickstudioeventsimulatorplugin.dylib`. Mapping to `-lquickstudioeventsimulatorplugin` and hoping for the best [-Wmap-unrecognized-libraries]
em++: warning: unrecognized file type: `/Users/marius/Qt/6.3.2/wasm_32/./qml/QtQuick/Studio/EventSystem/libquickstudioeventsystemplugin.dylib`. Mapping to `-lquickstudioeventsystemplugin` and hoping for the best [-Wmap-unrecognized-libraries]
wasm-ld: error: unable to find library -lquickstudioeffectsplugin
wasm-ld: error: unable to find library -lquickstudioapplicationplugin
wasm-ld: error: unable to find library -lquickstudioeventsimulatorplugin
wasm-ld: error: unable to find library -lquickstudioeventsystemplugin
em++: error: '/Users/marius/Documents/Git/emsdk/upstream/bin/wasm-ld #/var/folders/k3/prb53mjs50sf220pb_trz4fc0000gn/T/emscripten_7udnbcap.rsp.utf-8' failed (returned 1)
ninja: build stopped: subcommand failed.
I tried to build the components for other architectures or as a static library.

The realm dot net base example does not compile

I am having trouble at getting the example "QuickJournal" to compile on iOS. The code compiles OK, but fails during the Fody step.
Goals
Try out the example application for .NET through the following
- Pull the repository
- Open the solution in examples/QuickJournal
- Compile and test
Expected Results
Smooth compilation & testing experience
Actual Results
Fody out of memory exception
Steps to Reproduce
See the setup, follow steps
I am using the latest Xamarin/Visual Studio Mac/XCode
Code Sample
The regular realm source code
Version of Realm and Tooling
git clone https://github.com/realm/realm-dotnet.git
git checkout 8f5e36ffd91e06b9c60b91f9de3fb312b411a4a4
The exception I am getting is
Fody: Found debug symbols at '~/realm-dotnet/examples/QuickJournal/QuickJournal/obj/Debug/QuickJournal.pdb'.
MSBUILD : error : Fody: An unhandled exception occurred:
MSBUILD : error : Exception:
MSBUILD : error : Out of memory
MSBUILD : error : StackTrace:
MSBUILD : error : at (wrapper alloc) System.Object:AllocVector (intptr,intptr)
MSBUILD : error : at Microsoft.Cci.Pdb.MsfDirectory..ctor (Microsoft.Cci.Pdb.PdbReader reader,
See log file
RealmCompilelog.txt
Realm 1.2.1 addresses that by using an updated version of Fody.
Answer for older Realm versions:
This is caused by a Cecil bug with Mono 5.0. As Realm depends on Fody, which uses Cecil, compilation will fail for project referencing it. Until new Cecil and Fody versions are released, the workaround is to revert to Mono 4.8:

v-play installation - Cant deploy on desktop and device

I’ve just installed v-play but when i compile to desktop i get error :-1: error: cannot find -lGL and exits.
Then if i compile to android it will compile and install but the it never successfully opens the app and it exits on deployment.
These are the warnings i get :
Warnings while parsing QML type information of /home/theguy/V-Play/5.5/android_armv5/qml/QtCanvas3D:
/home/theguy/V-Play/5.5/android_armv5/qml/QtCanvas3D/plugins.qmltypes:1:24: Reading only version 1.1 parts.
/home/theguy/V-Play/5.5/android_armv5/qml/QtCanvas3D/plugins.qmltypes:10:5: Expected only Component and ModuleApi object definitions.
Warnings while parsing QML type information of /home/theguy/V-Play/5.5/gcc_64/qml/QtWebSockets:
/home/theguy/V-Play/5.5/gcc_64/qml/QtWebSockets/plugins.qmltypes:1:24: Reading only version 1.1 parts.
/home/theguy/V-Play/5.5/gcc_64/qml/QtWebSockets/plugins.qmltypes:10:5: Expected only Component and ModuleApi object definitions.
Warnings while parsing QML type information of /home/theguy/V-Play/5.5/gcc_64/qml/QtCanvas3D:
/home/theguy/V-Play/5.5/gcc_64/qml/QtCanvas3D/plugins.qmltypes:1:24: Reading only version 1.1 parts.
/home/theguy/V-Play/5.5/gcc_64/qml/QtCanvas3D/plugins.qmltypes:10:5: Expected only Component and ModuleApi object definitions.
And these are the compile issues I get:
15:03:42: Packaging error: Command “/home/theguy/Android/Sdk/platform-tools/adb -s 9cc172fdedea pull /system/bin/sh: readlink: not found /home/theguy/Desktop/Projects/v-play/ConverseLanguages/build-ConverseLanguages-Android_for_armeabi_GCC_4_9_Qt_5_5_0-Release/app_process” failed.Exit code: 1
15:03:42: Package deploy: Failed to pull “/system/bin/sh: readlink: not found” to “/home/theguy/Desktop/Projects/v-play/ConverseLanguages/build-ConverseLanguages-Android_for_armeabi_GCC_4_9_Qt_5_5_0-Release/app_process”.
15:03:42: Package deploy: Running command “/home/theguy/Android/Sdk/platform-tools/adb -s 9cc172fdedea pull /system/lib/libc.so /home/theguy/Desktop/Projects/v-play/ConverseLanguages/build-ConverseLanguages-Android_for_armeabi_GCC_4_9_Qt_5_5_0-Release/libc.so”.
Error while building/deploying project ConverseLanguages (kit: Android for armeabi (GCC 4.9, Qt 5.5.0))
When executing step “Deploy to Android device”
please see here for a reply: https://v-play.net/developers/forums/t/installation-problem-error-cannot-find-lgl/
Cheers, Chris

Qt: Building quazip/zlib Library error

I am statically building the quazip library as mentioned in the following post: linking QuaZip with Qt 4.8.0 into project
I get these error when I build the project:
/QtSDK/QtSources/4.8.0/src/3rdparty/zlib/zconf.h:373:6: error: "_LARGEFILE64_SOURCE" is not defined
In file included from ../../../quazip-0.4.4/quazip/zip.h:56,
from ../../../quazip-0.4.4/quazip/quazip.h:31,
from ../../../quazip-0.4.4/quazip/quazipfile.h:30,
from ../../../quazip-0.4.4/quazip/quazipfile.cpp:24:
/QtSDK/QtSources/4.8.0/src/3rdparty/zlib/zlib.h:1583:32: error: "_FILE_OFFSET_BITS" is not defined
cc1plus: warnings being treated as errors
Are these known errors in zlib library? I am using zlib library in Qt 4.8.0
That would be a bug in your compiler. I can't tell what version of zlib you're using, and your compiler does not show the offending line in the error message, so I can't tell exactly what the line contains. However I suspect that these are lines that have an #if directive with the noted symbol in the expression. Per the C standard, a symbol that is not defined is given a null value (no characters replace it) in an expression in an #if statement. Instead your compiler is erroneously issuing an error.

New Static Library has build error "libtool exited with code 1"

I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.

Resources