[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204031#action_204031
]
Dan Tran commented on MOJO-574:
-------------------------------
here is my proposal
1. Bundle up all include files found in source configuration, deploy it as a
special classifier with unique extension,
ie ${project.artifactId}-${project.version}-include.inczip
2. The user will need to make that artifact into dependency, the compiler mojo
will unpack it into ${project.build.directory}/native/include to be included as
system include path during compilation. Note it is tough if figure out if a
native dependency has include file bundle available for download.
3. We may need to implement http://jira.codehaus.org/browse/MOJO-1321 as well
BTW, NAR maven plugin could be another solution
> .h files as dependencies
> ------------------------
>
> Key: MOJO-574
> URL: http://jira.codehaus.org/browse/MOJO-574
> Project: Mojo
> Issue Type: New Feature
> Components: native
> Environment: Windows and Unix (Linux)
> Reporter: Tony Sandin
>
> To compile or link native code requires static or shared libraries and
> include files. THe current Native plugin only deploy share, static, or
> executable artifacts, but no include files.
> Includes files should deploy with the library artifact as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
