[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205564#action_205564
]
Rainer Schulze commented on MOJO-574:
-------------------------------------
Hello again and a Happy New Year from Germany!
Today I tried out the latest version of the native plugin on a linux platform.
Compiling and installing a couple of libraries (together with
<deployable>true</deployable>) was straightforward.
Then I wanted to build a library that is based on some of the other libraries.
In that build I could not see an additional include path in the compile
command, although I had entered an 'inczip' dependency. I guess this was not
intended.
I made another observation in the installled zip-Files. Not only the header
files are included, but also all the .cpp files. This seems also not to be
wanted.
Additionally I'm not very happy with putting all header files found anywhere in
the <source><directory>...</directory></source> area. Not all of the files
might be needed publicly. For me one of the most important features of maven is
the naming convention. So why should a stronger naming scheme not also be
'forced' to C or C++ development. The actual implementation of zipping all
header files in a source directory and its subdirectories might result in a
situation, where several 'packages' (libraries) offer 'defs.h' or 'globals.h'
and it is not clear for the compiler which one to use, where
'abc.xyz.org.lib/defs.h' would be much more precise .
I know that wishes like mines are simply to describe but eventually hard to
implement. But hopefully I could give you an idea about the problems you might
get without a certain naming convention.
I would like to hear from you.
And: thank you for the work already being done.
Rainer
> .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
