[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204035#action_204035
]
Dan Tran commented on MOJO-574:
-------------------------------
attach the include file bundle is optional, the mechanism to bungle to them up
is to gather all includes files under NativeSources[] configuration. Keep in
mind that a standalone include directory could be configure in one of
NativeSources object, and there for i dont see a need to create a standard
include directory. What we have now still work
Answer:
there definitely some platform specific include directories, we can add
configuration to filter, but I dont think it is a big deal to include them all.
I also rather not use other plugin to pull the include bundle, it must go thru
maven dependency management. Base on the extension, the plugin can decide if
unpack is necessary.
> .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
