Skip to content

Conversation

@JSUYA
Copy link
Member

@JSUYA JSUYA commented Aug 29, 2025

If custom_def.prop exists in the native path, it will be parsed and added to USER_LIB_PATH as the path.

If ./gen/custom_def.prop exists in the native path,
it will be parsed and added to `USER_LIB_PATH` as the path.
Copy link
Contributor

@seungsoo47 seungsoo47 left a comment

Choose a reason for hiding this comment

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

LGTM.
I'd like to add one thing.
How do you think about providing build_def.prop template like the project_def.prop?

@JSUYA
Copy link
Member Author

JSUYA commented Sep 1, 2025

How do you think about providing build_def.prop template like the project_def.prop?

Could you explain that in a bit more detail?
build_def.prop and project_def.prop are features provided by the Tizen CLI.
https://docs.tizen.org/application/tizen-studio/native-tools/project-conversion/

When user SO files exist in the Native Plugin, only the SO files located in the lib, lib/{arch}, and lib/{arch}/{version} paths are packaged together.
This format is maintained in most cases.

I had expected to be able to use it when a separate LIBS was needed.
However, since it is not an official file, I will apply this patch after further consideration.

@JSUYA JSUYA marked this pull request as draft September 1, 2025 10:31
@JSUYA JSUYA closed this Sep 1, 2025
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