[
http://jira.codehaus.org/browse/MOJO-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204139#action_204139
]
Dan Tran commented on MOJO-1435:
--------------------------------
using compilerOutputDirectory is the way to go, since it is generic for all
compilers. Putting obj files at target directory also work too, dont you
think? If the user want it to be at somewhere else, he/she can set it. The key
here is it should work out of the box regardless where the output are.
I was about to checkin your maven-native-gcj component, but it just does not
change much, and generic-c still work from what I see.
let's see how your phase 2 turn out, i would expect it to put more behavior
than the current generic-c
> Support for Java compiler GCJ
> -----------------------------
>
> Key: MOJO-1435
> URL: http://jira.codehaus.org/browse/MOJO-1435
> Project: Mojo
> Issue Type: New Feature
> Components: native
> Reporter: Marco Lessard
> Attachments: MOJO-gcj-maven-native.patch
>
>
> Added Compiler/Linker providers for GCJ.
> - Implemented useOutputDirectory so *.o go to target/objs . Default to false
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
