On 8/8/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> On Mon, Aug 08, 2005 at 06:44:28PM -0700, dan tran wrote:
> > I am currently porting M1 maven-native-plugin with cpptask
> > to M2 mojo. And I am also in  the process of perform a few more refactorings
> > and check in to org.codehaus.mojo as prelimary code for review
> >
> > I can see lots of reuseable code we can share between .net plugin and
> > native plugin such as
> >
> >     - dependency analysis.
> 
cpptask has  a source parser that looks for #Include #import for dependencies
analysis. I have not looked in details what it has for .net yet.

> What do you mean?
> 
> >     - handling of .dll and .exe types for install/deploy purposes
> 
You could be right, .net dll and exe has a smaller scope then 
the native one which has lot of extension types (.dll, .exe, .lib, .pdb,
.so, .si, .a and more)


> A .NET .dll really isn't the same thing as a native .dll and probably
> shouldn't the same artifact handler. A native .dll/.exe handler has to
> include the processor/os/etc platform while a .net .dll doesn't have to.
> 
> >     - Similar creation of Commandline to invoke the compiler/linker
> 
> Hopefully the Commandline stuff in plexus-utils and/or the new
> commons-exec component should contain anything that's commons here. Or am
> I missing something? I assume that you're going to have to have a custom
> output parser for each type of compiler (GCC, MC C/C++, ..)
> 
> --
I base on my comandline base on plexus-util's Commandline, so we are not 
different here. but how to construct the command line should be similar
between .net and the native on ( executate +options + outputfie)

There is no parser for compiler ouput.  I only check for the exist code.


> Trygve
> 
> 

-Dan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> 
> iD8DBQFC+A284EbM92cyCUURApPDAJ4gEiWVcVEEjIhLWP+qkaW9z7YVXACgpGmf
> Xq4FurvUKT7GE2sNVzsIV0M=
> =AhhL
> -----END PGP SIGNATURE-----
> 
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to