[
http://jira.codehaus.org/browse/MOJO-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204138#action_204138
]
Marco Lessard commented on MOJO-1435:
-------------------------------------
Thanks,
Sorry I'm not responding fast but it is holiday time for the family...
You're right, it was working fine with the generic-c except for the specific
params for GCJ, so I followed your path by creating a gcj compiler which is
more flexible for extensions.
I don't agree to put the compilerOutputDirectory in the POM, it should actually
be set as default for all gcj projects (and even C projects), since it is the
way maven works, all java programmers are used to work and also all java tools
for maven. So I created the useOutputDirectory property to activate the /objs
which is quite convenient.
As I told you, I've been working on a phase II extension plugin for gcj so we
can use it in a JAR project type so we can generate both java binary and native
binary in the same build.
> 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
