Skip to content
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.

[Feature request] better way to expose header files to downstream projects. #15255

Open
roywei opened this issue Jun 16, 2019 · 2 comments
Open

[Feature request] better way to expose header files to downstream projects. #15255

roywei opened this issue Jun 16, 2019 · 2 comments
Labels
Build CI Feature request

Comments

@roywei
Copy link
Member

roywei commented Jun 16, 2019 •
edited
Loading

Follow up on: #15213
Related issue: #15211

We need better ways to expose header files(including MXNet dependencies) to the downstream projects.
@mxnet-label-bot
Copy link
Contributor

Hey, this is the MXNet Label Bot.
Thank you for submitting the issue! I will try and suggest some labels so that the appropriate MXNet community members can help resolve it.
Here are my recommended labels: Test, Feature

@roywei roywei changed the title [Feature request [Feature request] better way to expose header files to downstream projects. Jun 16, 2019
This was referenced Jun 16, 2019
Closed
Merged
@leleamol
Copy link
Contributor

@roywei , I noticed in the mkldnn.mk, we are already copying the header file to $(MXNET_INCDIR) folder.

@mxnet-label-bot add [CI, Build, Feature Request]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Build CI Feature request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@roywei @marcoabreu @leleamol @mxnet-label-bot