Standards for native libraries

[GoogleCodeExporter]

What is the correct (Ivyroundup standard) for including native libraries?

For instance GWT 1.7.0 depends on a native SWT libraries.
http://code.google.com/p/ivyroundup/source/browse/trunk/src/modules/com.google/g
wt/1.7.0/ivy.xml

That ivy module uses artifacts to describe the native libraries. Is that the 
standard method for doing this in ivyroundup?

Thanks

David

Original issue reported on code.google.com by stu3b3 on 25 Jan 2013 at 3:20

[GoogleCodeExporter]

Yes... ivy supports non-Java stuff in the same way as Java stuff. That module 
is a good example of how to do it.

We just use the extension accordingly, e.g., "so", "dll", "jnilib", etc.

These should be put into separate ivy configurations and usually not part of 
"default".

Original comment by archie.c...@gmail.com on 25 Jan 2013 at 3:40

• Changed state: Fixed
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Could these comments be added to the Maintainer Guidelines?
http://code.google.com/p/ivyroundup/wiki/ModuleMaintainerGuidelines

Currently the guidelines say not to use the artifact tag. Presumable one is
supposed to read between the guidelines when dealing with native libraries?

David

Original comment by stu3b3 on 25 Jan 2013 at 4:15

[GoogleCodeExporter]

The guidelines say: "avoid using <artifact> sub-tags in dependencies".

You must certainly use them within the <publications> tag..!

Original comment by archie.c...@gmail.com on 25 Jan 2013 at 4:26