Alexander Neundorf wrote:
5. On my Windows box, I cd into build/src, and I type the
same(ish) commands, to have a build made under build/win32.
Yes. But that depends what you want to use for building: MSVC, cl+nmake,
mingw, ...
Right. By default cmake seems to produce a .sln file and
a
On Nov 14, 2007 1:02 PM, Stephen Collyer [EMAIL PROTECTED] wrote:
Presumably some switch makes it produce
something suitable for nmake ?
That would be -GNMake Makefiles.
--
Salvatore Iovene
http://www.iovene.com/
Key Fingerprint: 5647 944D D5AD 2E87 00B4 7D54 2864 359D FF20 16D8
Alexander Neundorf wrote:
..and you need to include(CPack) and maybe set some cpack variables, see
here for more info: http://www.cmake.org/Wiki/CMake#CPack
I can't see from the example on that page how Cpack knows what to
package up - is it simply the set of items that have previously
been
On Wednesday 14 November 2007, Stephen Collyer wrote:
Alexander Neundorf wrote:
...
Yes, it's the install target.
I guess I need to add some specific install related code
to the CMakeLists.txt files to get that target ?
Yes.
You need to add the INSTALL() commands to get this target.
7.
I am almost a total cmake newbie. I've been looking through
the wiki for information on how one actually performs a cross-platform
build with cmake, but I can't find any. Can someone tell me if my
thinking outline here makes sense:
1. Let's assume I want to do a Linux and Win32 build from the
On Tuesday 13 November 2007, Stephen Collyer wrote:
I am almost a total cmake newbie. I've been looking through
the wiki for information on how one actually performs a cross-platform
build with cmake, but I can't find any. Can someone tell me if my
thinking outline here makes sense:
1. Let's
On 11/13/07, Stephen Collyer [EMAIL PROTECTED] wrote:
1. Let's assume I want to do a Linux and Win32 build from the
same source tree.
2. I have a directory tree like:
./src/whatever
./build/linux
./build/win32
./install/linux/whatever
./install/win32/whatever
All of my cross-platform source
