Skip to content

Conversation

cortinico
Copy link
Member

@cortinico cortinico commented Sep 7, 2022

Summary:

Power library authors might want to specify a custom CMake path. Currently we've been reusing the androidMkPath config key assuming that the CMake file would be in the same folder (which is a sound assumption). However we should be more precise here and allow users to specify a custom cmakeListsPath if they want.

Test Plan:

@thymikee not sure how can we test this as the change is touching several files.

libraryName?: string | null;
componentDescriptors?: string[] | null;
androidMkPath?: string | null;
cmakePath?: string | null;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think cmakeListsPath would make more sense due to being more explicit? I'm good with both, but have a slight favor for explicitness

Copy link
Member

@thymikee thymikee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks! One lint error to resolve and a decision whether to go with cmakPath or cmakeListsPath to make

@cortinico
Copy link
Member Author

Looks good, thanks! One lint error to resolve and a decision whether to go with cmakPath or cmakeListsPath to make

Yup better be explicit

@thymikee thymikee changed the title Add support for explicit cmakePath in react-native.config.js Add support for explicit cmakeListsPath in react-native.config.js Sep 7, 2022
@thymikee thymikee merged commit 4a6e64d into main Sep 7, 2022
@thymikee thymikee deleted the nc/cmake-path branch September 7, 2022 15:45
@thymikee
Copy link
Member

thymikee commented Sep 7, 2022

Released 9.1.0 with this change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants