On Tuesday, 21 November 2023 08:43:20 PST DAS Loop wrote:
> Yes Thiago, CMAKE_TOOLCHAIN_FILE is the way but vcpkg is doing the same.
Either vcpkg knows about building for WASM or it doesn't.
If it does, then its toolchain file is the one you want and it will produce
WASM content.
If it doesn't,
Yes Thiago, CMAKE_TOOLCHAIN_FILE is the way but vcpkg is doing the same.
QT_CHAINLOAD_TOOLCHAIN_FILE works (more or less), thanks Alexandru.
Thanks,
David
On Tue, Nov 21, 2023 at 4:26 PM Thiago Macieira
wrote:
> On Tuesday, 21 November 2023 06:04:36 PST DAS Loop wrote:
> > The app is compiled
On Tuesday, 21 November 2023 06:04:36 PST DAS Loop wrote:
> The app is compiled for wasm as expected.
>
>
> Because I´m using vcpkg, using CMAKE_TOOLCHAIN_FILE is not a solution for
> me.
>
>
> Any idea of what is wrong?
If you're cross-compiling, you MUST use CMAKE_TOOLCHAIN_FILE.
--
Thiago
Hi,
Configure with
cmake -B build -G Ninja -S .
-DCMAKE_TOOLCHAIN_FILE=/Users/Shared/Qt6.2.0/6.6.0/wasm_singlethread/lib/cmake/Qt6/qt.toolchain.cmake
-DQT_CHAINLOAD_TOOLCHAIN_FILE=
> On 21. Nov 2023, at 15:04, DAS Loop wrote:
>
>
> Hi,
>
> I have a small test for wasm using cmake that co
Hi,
I have a small test for wasm using cmake that compiles only for the main
architecture (in my case macOS).
With Qt installed in the following paths:
- /Users/Shared/Qt6.2.0/6.6.0/macos
- /Users/Shared/Qt6.2.0/6.6.0/wasm_singlethread
If I generate the build with:
cmake -B build -G Ninja -S .