Instead of setting up your compiler/linker command line environment prior running maven to build your artifact, you can use <envFactoryName> to configure one of the following built-in environments:
This feature is extremely useful when you have a need to use various compilers in your build system and it is impossible to set up single global environment to accommodate all compilers.
The following example shows how to configure MSVC 2003
<project>
....
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>native-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<compilerProvider>msvc</compilerProvider>
<envFactoryName>org.codehaus.mojo.natives.msvc.MSVC2003EnvFactory</envFactoryName>
...
</configuration>
...To create your own environment factory, package your own implementation of EnvFactory interface into a jar, and have the jar as this plugin's dependency.
<project>
....
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>native-maven-plugin</artifactId>
<extensions>true</extensions>
<dependencies>
<dependency>
your EnvFactory package
</dependency>
</dependencyies>
<configuration>
<envFactoryName>myFactory</envFactoryName>
...
</configuration>
...