firebase / firebase/firebase-cpp-sdk

[Question] How to create prebuilt version of sdk from scripts

Open
#1,685 1 comment 1 reaction 0 assignees View on GitHub
needs-triage new type: question
Dominant language
C++
Stars
326
Forks
137
Avg merge
3d 9h
Merged PRs (30d)
5

Description

### [READ] For Firebase Unity SDK question, please report to [Firebase Unity Sample](https://github.com/firebase/quickstart-unity/issues/new/choose)

Once you've read this section and determined that your issue is appropriate for this repository, please delete this section.

### [REQUIRED] Please fill in the following fields:

* Pre-built SDK from the [website](https://firebase.google.com/download/cpp) or open-source from this repo: open-source from this repo
* Firebase C++ SDK version: 12.5.0
* Main Firebase Components in concern: all
* Other Firebase Components in use: all
* Platform you are using the C++ SDK on: Linux
* Platform you are targeting: desktop (iOS, Android, and/or desktop)

### [REQUIRED] Please describe the question here:

What's up guys. Sorry for stupid (maybe) question.

I build firebase sdk from sources.
How can I get prebuilt versrion of sdk from script?

I invoke:
`./build_scripts/desktop/package.sh -b /home/era/Work/firebase-cpp-sdk/build -o /home/era/Work/firebase-cpp-sdk/release -p linux -t /usr/bin -j 28 -L`

But, there are no some include files and folders. Here what i get.

![Image](https://github.com/user-attachments/assets/7d1147f0-268d-42e3-bda5-04170f70122f)

![Image](https://github.com/user-attachments/assets/6ed2fb8f-5ef2-4ad6-a451-9b743ffc5540)

But, if we look at the prebuilt version of sdk (zip file) you will see more files
For ex, the include files from prebuilt version

![Image](https://github.com/user-attachments/assets/a9088ce0-201e-473b-8485-62f944393b6b)

As you can see, there are more files.
What I do wrong?

Contributor guide

Open the contributing guide

Research direction

Start with build_scripts/desktop/package.sh and reproduce the supplied command using the stated build and output paths. Compare its generated include tree with the downloaded prebuilt SDK and trace which packaging inputs control the differences. Done means identifying the correct invocation or documenting the repository-side packaging gap.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, cpp
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.