[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205861#action_205861
]
Rainer Schulze commented on MOJO-574:
-------------------------------------
o.k. - you put the 'includes' into the first part of the name, thus avoiding
the 'inczip'.
BTW: Wouldn't it be a (first) good practice to extract the header files
temporarily into 'target/lib/projectname/...' (not only 'target/lib') By this
means several 'defs.h' or something like this won't go into the same directory
(and override previously unpacked files with the same name). But anyway: the
resulting problem will be how to set the include path in the compile command.
Dan, FYI: Analyzing the way you set up your IT was very informative for me.
Especially the 'activation' mechanism and the 'module' techniques were new for
me! I hope that this newly acquired knowledge will influence my next projects
;-)
> .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
> Assignee: Dan Tran
>
> 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
