having .h files as dependencies is not possible as this moment. The
main problem here is how you would know which one is really include
files, user may want .c, .hpp as include file as well.
Also the pom will be polluted with lots of .h dep
One work around is to package .h files in a compressed form to be your
pom dependency file and use maven-dependency-plugin to unpack them
into a location under target directory, then reference the native
source path to pick them up.
-D
On Wed, Mar 4, 2009 at 12:41 AM, Rémy Sanlaville
<remy.sanlavi...@gmail.com> wrote:
> Hi Dan,
>
> The mentioned test phase is for java test.
>
> True and it why i was surprise that native-maven-plugin is linked to it.
>
>
>> Take a look at jade native
>> maven plugin, it is an spin off of native plugin and covers cppunit
>> test
>
> Thanks, I wasn't aware of this plugin. We will have a look.
>
> I wonder also how to manage C interfaces (.h) with this plugin.
> As I can see in configuration example (cf. [1] and [2]), we have to include
> them in the source path:
> <source>
> <directory>${native.source.dir}/include</directory>
> </source>
>
> I don't like it to much because we have to specify a path directory.
> I rather prefer to use a dependency (it's really better if you have
> different modules/projects).
> Isn't it possible ?
>
>
> Rémy
>
> [1]
> http://mojo.codehaus.org/maven-native/native-maven-plugin/examples/share-lib.html
> [2]
> http://www.jfrog.org/sites/jade-plugins/1.3/jade-plugin-parent/jade-build-plugin-parent/jade-native-plugin/examples/static-lib-ranlib.html
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
