Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

emscripten and protobuf dependency #181

Open
gmabey opened this issue Dec 1, 2020 · 6 comments
Open

emscripten and protobuf dependency #181

gmabey opened this issue Dec 1, 2020 · 6 comments
Assignees
Labels
question Further information is requested

Comments

@gmabey
Copy link
Contributor

gmabey commented Dec 1, 2020

I imagine the answer to this question might be obvious if I knew more about protobuf, but -- today I'm working to compile qtprotobuf using emscripten, towards targeting my application for wasm. I'll be sure to post some notes about how to accomplish that if I'm successful.

In the course of doing so, I'm now working to build all dependencies to facilitate that. Building Qt was pretty easy, as it's a supported platform. Next is protobuf, which just made me start to wonder why it's a dependency. Like, it would be a significant simplification for this kind of cross compiling effort if only protoc were needed. It's surely more complicated
than that, right?

Also -- is it feasible to build qtprotobuf without grpc support?

@gmabey gmabey added the question Further information is requested label Dec 1, 2020
@semlanik
Copy link
Owner

semlanik commented Dec 7, 2020

About crosscompilation, in regular case you don't need protoc built for target system, since it's generator supposed to be ran on host system only. Same for qtprotobufgen. It should be compiled for host system only while crossconpiling whole project. About conditional compilation without grpc support, I think that what need to be added to build procedure. Will to it soon.

@gmabey
Copy link
Contributor Author

gmabey commented Dec 28, 2020

That is excellent news, and I think it will make it easier for others to use qtprotobuf also, since it will have fewer required dependencies.

Would you please consider assigning a milestone to this feature, so that I can have some idea as to when it may be available?

@semlanik
Copy link
Owner

semlanik commented Dec 28, 2020

I planned it for 0.6, but deadline for 0.6 is crossed and I have no time to complete it this year, unfortunately. Probably 0.7 is what I could promise and only next spring. Here is task #149

@gmabey
Copy link
Contributor Author

gmabey commented Dec 28, 2020

Ok -- that's helpful for me to know that much at least.

gmabey referenced this issue Mar 8, 2021
- It doesn't make sense to keep type-traits for convertes.
  All integral types suppose to be converted from/to any integral
  type. Add extra converters to qulonglong and qlonglong types.
- Remove the extern keyword for the functions that are explicitly
  defined in header files.
- Add symbols export for the library that contains unversallistmodel.
- Add optional serializer result for QMatrix4x4 and QTransform.
- Temporary disable grpc tests on Windows
- Add windows workflow for pull requests
@semlanik
Copy link
Owner

semlanik commented Mar 9, 2021

@gmabey, have a question probably not directly related to the issue. Did you manage to make the network stack work in the wasm environment? Since the last time I tried network stack from wasm, it was blocked by chrome and ff.

@gmabey
Copy link
Contributor Author

gmabey commented Mar 9, 2021

No, I just stopped work on it at that point. I might be able to try out that experiment tonight though -- it's a critical step that we'll have to figure out eventually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants