Another thought is to take a look at NAR and native-plugin to see if you can find a solution not to relinking when there is no change in source and provide patch
-Dan On Tue, Mar 1, 2011 at 10:07 AM, sintetik <sintet...@gmail.com> wrote: > Thank you Mark, > >> NAR also links in the compile phase as it uses cpp-tasks to handle uniform >> compilation and linking. > > I guess it means linking will be repeated anyhow even if code didn't change? > > I had a thought that it's theoretically possible to resolve my problem > (redundant linking) by creating 2 projects (for every cpp module), one of > them doing compilation and producing obj files and second one just depending > on the first one and performing linking. > > This looks somehow ugly though, so I'm thinking about possibility to > "virtualize" this process inside the plugin itself. > > Please let me know whether you think if it's possible or any other > considerations. > > Thanks, > Sergey. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/c-native-maven-plugin-redundant-linking-at-second-run-problem-tp3403291p3405441.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
