firebase / firebase/firebase-cpp-sdk

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

Abierto
#1,685 1 comentario 1 reacción 0 asignados Ver en GitHub
needs-triage new type: question
Lenguaje dominante
C++
Estrellas
326
Forks
137
Merge medio
3 d 9 h
PR fusionados (30 d)
5

Descripción

### [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?

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
bash, cpp
Área
build-system
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
20/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.