[
http://jira.codehaus.org/browse/MOJO-1109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin von Gagern updated MOJO-1109:
------------------------------------
Attachment: generic-windmc-windres.patch
OK, I had to make two test classes abstract in fact, not only in name, for
surefire to accept them and not complain about classes with missing tests. With
that modification, I managed to compile and test a
maven-native-1.0-alpha-3-SNAPSHOT. Seems to work well enough.
> Support mingw toolchain
> -----------------------
>
> Key: MOJO-1109
> URL: http://jira.codehaus.org/browse/MOJO-1109
> Project: Mojo
> Issue Type: New Feature
> Components: native
> Environment: Gentoo Linux
> Reporter: Martin von Gagern
> Attachments: generic-windmc-windres.patch,
> generic-windmc-windres.patch
>
>
> I would very much like to have a mingw toolchain, so that I can cross-compile
> Windows applications on Linux.
> For that I would need several things:
> 1. compiler and liker like generic, but with mingw32-gcc as executable.
> This can be done in the pom by specifying all the executable names, but that
> is rather tedious.
> You might consider a more general approach to cross compilers, making target
> architecture a pom element, and configuring the comoilers appropriately.
> Would require major surgery, I guess, but might be worthwhile in terms of
> portability.
> 2. mingw32-windmc as resource compiler.
> The interface seems to be pretty much that of the msvc mc, so this can again
> be achieved in the pom. If you introduce a new provider for other components,
> it would seem reasonable to provide the resource compiler as well.
> 3. mingw32-windres as message compiler.
> The command line syntax is a bit different from msvc, using -I for include
> directories and -o for output file. So far things can be changed by providing
> a new component. Compiler works well enough, but the gcc linker won't accept
> the .res file it generated. Instead, mingw-windres usually generates object
> files. As the file extension "res" seems to be hardcoded into the
> ResourceCompilerConfiguration, this would require a change to the API.
> I'll attach a patch for 2. and 3., although I couldn't test it here, because
> the api tests fail even without any modifications, in
> maven-native-1.0-alpha-2 as well as in current trunk. I'll try to
> inverstigate these build errors tomorrow, and update my patch if required.
> For the cross compiling issue, 1., I'd like a few more comments before I
> start coding.
--
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
