[Question] How to compile the Release build?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cmake, cpp, unreal-engine
- Domain
- build-system
Research direction
Start by reproducing the documented CMake configure and build commands for the firebase_analytics target with CMAKE_BUILD_TYPE=Release on Windows. Inspect the generated Debug and Release output locations and the MSVC iterator-debug-level settings, then verify that both configurations produce libraries that link with the corresponding Unreal Engine build without LNK2038.
Written by the indexing model from the issue text.
Description
[REQUIRED] Please fill in the following fields:
- Pre-built SDK from the website or open-source from this repo: build locally
- Firebase C++ SDK version: 11.8.0
- Main Firebase Components in concern: Mainly analytics (Auth, Database, etc.)
- Other Firebase Components in use: -
- Platform you are using the C++ SDK on: Windows, VS 2019 (build tools v142) and Unreal Engine 4.27
- Platform you are targeting: Windows
[REQUIRED] Please describe the question here:
After fullfilling the requirements, I run the build with these command
> mkdir firebase_analytics_build && cd firebase_analytics_build
> cmake -DCMAKE_BUILD_TYPE=Release -DOPENSSL_ROOT_DIR="C:\Users\herpi\Downloads\OpenSSL-3.3.0-Win-pc064\OpenSSL\OpenSSL\3.3.0" -A x64 ..
> cmake --build . --target firebase_analytics -DCMAKE_BUILD_TYPE=Release
The lib file is generated but it's always under the Debug prefix directory. In my case, this debug library will lead to this error while linking the library in my UE4 project.
firebase_app.lib(variant.obj) : error LNK2038: mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '2' doesn't match value '0' in SharedPCH.UnrealEd.ShadowErrors.h.obj
How to build both Release and Debug?
Thank you in advance.
- Dominant language
- C++
- Stars
- 326
- Forks
- 138
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from firebase/firebase-cpp-sdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
firebase/firebase-cpp-sdk#1905 · 2 comments ·
-
api: firestore
Difficulty 5/5 Over a week Newbie friendliness 35/100
firebase/firebase-cpp-sdk#1920 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 70/100
firebase/firebase-cpp-sdk#1904 · 1 comment ·
-
new type: question
Difficulty 4/5 3-5 days Newbie friendliness 45/100
firebase/firebase-cpp-sdk#1892 · 1 comment ·
-
nightly-testing
Difficulty 4/5 3-5 days Newbie friendliness 25/100
firebase/firebase-cpp-sdk#1859 ·
All issues in firebase/firebase-cpp-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/message_filters#338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
subsurface/subsurface#4984 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·