So, you just have to include the DUMMY part, but the resulting file name does not include it?
Anyhow, as you have some experience in studying the code, what would you say how difficult is it to include a new compiler that is not currently supported by the nar? I read that NAR is using the ant cpptasks for calling the native compilers. Is it just adding a new xml entry somewhere or do I have to modify the plugin itself? Thanks, Jan -----Ursprüngliche Nachricht----- Von: Jörg Schaible [mailto:[email protected]] Gesendet: Dienstag, 18. August 2009 09:19 An: [email protected] Betreff: Re: AW: Re: RE : AW: RE: AW: Re: AW: Re: Maven for Non-Java Projects Hi Jan, Jan Wedel wrote at Dienstag, 18. August 2009 08:52: [snip] > @ Jörg: > > Could you please also post an excerpt of the "demo-dll"-project POM and > how you specify different classifiers in the first place? ================ %< ================ <project> [...] <groupId>com.acme.demo</groupId> <artifactId>demo-dll</artifactId> <packaging>nar</packaging> [...] <plugin> <groupId>org.freehep</groupId> <artifactId>freehep-nar-plugin</artifactId> <configuration> <runtime>static</runtime> <linker> <name>msvc</name> </linker> <libraries> <library> <type>shared</type> </library> </libraries> <c> <optimize>speed</optimize> </c> </configuration> </plugin> [...] </project> ================ %< ================ So, actually we do not define the classifier, it is auto-generated by the nar plugin based on the environment in use. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
