[
http://jira.codehaus.org/browse/MOJO-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205570#action_205570
]
Dan Tran commented on MOJO-574:
-------------------------------
the inczip dep is expanded under target/native/include
here a log from build linkages IT under win32, you should see the the above
path included in the output
[INFO] cmd.exe /X /C "cl.exe /MD /W4 -IC:\Users\dantran\dev\mojo\maven-native\na
tive-maven-plugin\src\it\linkages\src\main\native -IC:\Users\dantran\dev\mojo\ma
ven-native\native-maven-plugin\src\it\linkages\win32\ExeStatic\target\native\inc
lude /FoC:\Users\dantran\dev\mojo\maven-native\native-maven-plugin\src\it\linkag
es\win32\ExeStatic\target\objs\hello.obj -c C:\Users\dantran\dev\mojo\maven-nati
ve\native-maven-plugin\src\it\linkages\src\main\native\hello.c"
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
Copyright (C) Microsoft Corporation. All rights reserved.
to not include unintended file in inczip, it is best that you to align your
source
tree to have a dedicated include directory with include files only, ie you only
want
to provide interface to outside of your library only. I think this is
the best practice for any library. However best practice can be hard to adjust
about the collision of same name is something i dont know how to address yet.
perhaps
the user may want to adjust the file name/path to make it unique where inczip
files are
all unpacked on the same directory ( target/native/include )
regarding convention, the plugin tries not to be aware and let use to set the
to be compiled file under source' fileNames or include/excludes. it may be
sufficient
Thanks for try it out
> .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
