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

Export functionality used in Flutter Engine to public headers #34547

Closed
mehmetf opened this issue Sep 21, 2018 · 8 comments
Closed

Export functionality used in Flutter Engine to public headers #34547

mehmetf opened this issue Sep 21, 2018 · 8 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-task

Comments

@mehmetf
Copy link
Contributor

mehmetf commented Sep 21, 2018

Currently, Flutter engine is using the following private Dart headers:

#include "third_party/dart/runtime/bin/crypto.h"
#include "third_party/dart/runtime/bin/io_natives.h"
#include "third_party/dart/runtime/bin/embedded_dart_io.h"

Please migrate the functionality used by https://github.com/flutter/engine/blob/master/lib/io/dart_io.cc and by https://github.com/flutter/engine/blob/master/lib/ui/dart_runtime_hooks.cc to common Dart headers so these can be converted to third_party/dart/runtime/include/ paths.

This prevents Flutter engine from being compiled in Google.

@mehmetf
Copy link
Contributor Author

mehmetf commented Sep 21, 2018

@zanderso @mraleph FYI

@zanderso zanderso added area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-task labels Sep 21, 2018
@zanderso
Copy link
Member

@a-siva This is the header file issue we discussed.

@mehmetf @keertip would it work for you if we captured the needed API in a public header under runtime/bin/include ?

@mehmetf
Copy link
Contributor Author

mehmetf commented Sep 21, 2018

Hm, I will leave the final answer up to @keertip however the way we recommend these headers be used now is:

#include <dartapi.h>

which implies there's a collision possibility if we start including files from different dirs.

@a-siva
Copy link
Contributor

a-siva commented Sep 22, 2018

You mean 'include <dart_api.h> ?

This include file should probably be called something else, maybe 'dart_embedder_api.h'

@chinmaygarde
Copy link
Member

What is the utility of dart_embedder_api.h over dart_api.h? Are they same?

@mehmetf
Copy link
Contributor Author

mehmetf commented Sep 26, 2018

I just wanted to highlight that this is blocking an active project. It would be great to get a timeline on this fix. Is it something doable in the next week or so?

@a-siva
Copy link
Contributor

a-siva commented Sep 26, 2018

Ben is slated to start work on this, we are in the process of scoping the work and will update with a timeline here.

@bkonyi
Copy link
Contributor

bkonyi commented Oct 2, 2018

This change landed last week in this CL.

@bkonyi bkonyi closed this as completed Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. type-task
Projects
None yet
Development

No branches or pull requests

5 participants