> - Using again the native plugin, create a multi-module project. The > parent would contain the C++ source code, while each child module would > be devoted to create a single OS/platform specific artifact.
I use this option. However you still need to use profile to do debug/release type artifacts
I'm not so sure this is going to be as simple as that. C/C++ artifacts are not nearly as nice and tidy as java artifacts. A java artifact is essentially a single file, the .jar file. A C/C++ artifact will be at minimum two files: the library and the header file(s). In addition to that, you will likely need to know the exact compilation options used to compile the code and to link the shared object, so you can match these in your actual project build. The compilation will need to know about your local repository location and set multiple classpath type parameters to point to the right headers and libraries. It would be a great thing to have, but having spent a significant amount of time developing C/C++ build systems, I can guarantee some interesting challenges. I don't think that maven is quite up to it yet, but it is certainly an interesting approach to build avoidance. -- cg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
