Hello Eric,
thank you very much for your very quick response. Yes, I am willing to
write some documentation on the Wiki as soon as I have understood the
basic principles of how to make a package.
Eric Noulard wrote:
Write you CMakeLists.txt
make it work for:
1 - compiling your project (i.e. no error when calling 'make')
This already works on my machine.
2 - installing your project (i.e. no error when calling 'make install')
This does not. I have no target "install". Browsing through
http://www.cmake.org/HTML/WritingCMakeLists.html
http://www.cmake.org/HTML/Examples.html
I discover nothing about how to create this target. I suppose (sorry for
my stupidity) it has something to do with the INSTALL command mentioned on
http://www.cmake.org/HTML/Documentation.html
I have already played a bit with this, by means of trial and error, but
frankly speaking, I do not understand the documentation of INSTALL or
INSTALL_FILES (moreover, I do not want anything to be installed, I just
want to have a.h, a.cpp, b.h, b.cpp, main.cpp compiled and packaged for
delivery). Maybe I understand something completely wrong here.
The customer should do:
1 - unpack i.e. tar zxvf <packagename>.tar.gz
which creates
2 - create a build tree
run cmake
So the customer MUST have cmake installed!?
We did add a paragraph on this in our TSP Programming Tutorial:
http://download.savannah.nongnu.org/releases/tsp/documentations/tsp_programming_tutorial-1.0.pdf
Nice document. And you write at the very beginning:
"1. Check you have the CMake installed (see A.1)."
OK, this answers my question! (Chances are high that my customer will
not accept this, but that's his problem :-) )
I may write a CMake+CPack primer if I found time.
I may review yours if you write one :=)
This is what I call an offer!
Thank you again,
Joachim
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
