Building the package target after installing the NSIS installer is all there is to it. It's very easy if you have the time and a build machine to do it...<div><br><br><div class="gmail_quote">On Thu, Dec 18, 2008 at 9:16 AM, Brad King <span dir="ltr"><<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="Ih2E3d">Roman Yakovenko wrote:<br>
> On Wed, Dec 17, 2008 at 1:33 PM, Brad King <<a href="mailto:brad.king@kitware.com">brad.king@kitware.com</a>> wrote:<br>
>> FYI, there is a CPack configuration available in the gccxml checkout.<br>
>> You can create your own installer using CPack's NSIS generator.<br>
><br>
> Can you point me to the documentation or explain how I can do this?<br>
><br>
> I build GCCXML on Linux and Windows almost every time you fix<br>
> something. I have no problem to build installer and upload it to<br>
> SourceForge.<br>
<br>
</div>Basic CPack documentation (which also comes in its man page) is here:<br>
<br>
<a href="http://www.cmake.org/cmake/help/cpack2.6docs.html" target="_blank">http://www.cmake.org/cmake/help/cpack2.6docs.html</a><br>
<br>
The gccxml source already has all the configuration files. On linux<br>
with CMake 2.6 you can just run<br>
<br>
make package<br>
<br>
On Windows you need to install NSIS and then run CMake and build gccxml.<br>
There should be a PACKAGE target in VS or "make package" in MSYS. FYI,<br>
Dave Cole (Cc-ed) implemented the package configuration rules in gccxml.<br>
<font color="#888888"><br>
-Brad<br>
</font></blockquote></div><br></div>