Our (many) MSVS 2003 Projects are configured with XXXXX.vcproj files (Visual C Project). These files are what hold all the configuration and build instructions for the cpp project... yadda yadda yadda. Can I get the native provider to look at this file? Because really, this is what we want... I don't want the maven and cpp visual studio configuration to diverge and fall out of whack. The compilers should be the same.
Cheers, Andrew On Thu, Aug 14, 2008 at 11:09 PM, Dan Tran <[EMAIL PROTECTED]> wrote: > native plugin does not use devcom, it uses MS compiler directly thru > envFactoryName > > there should be plenty to example in IT test cases if you pull the source. > > -D > > On Thu, Aug 14, 2008 at 12:28 AM, Andrew Hughes <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > I'm trying to replace the following ant target to build some microsoft > > visual studio .net 2003 code. I am not a c++ person so I don't really > know > > what I am talking about! However there isn't any examples with the > > "Devenv.com" on the maven native site ( > > http://mojo.codehaus.org/maven-native/native-maven-plugin/). I'm not > sure if > > the 2003 compiler is supported. > > > > Thanks fore reading.... on with the ant script. > > > > <target name="build.exe" description="Compile to exe"> > > <exec executable="Devenv.com" dir="${module.path}" failonerror="true"> > > <arg line="/build release "${module.name}.sln"" /> > > </exec> > > <copy file="${module.path}\Release\${module.name}.exe" > > todir="${module.output.dir}" /> > > </target> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
