use ccmake instead of cmake (or use the GUI) - the config names it
displays can be used with -D on the cmake command line.
On 9/19/08, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> Guillaume Lelarge wrote:
>> Magnus Hagander a écrit :
>>> Guillaume Lelarge wrote:
Magnus Hagander a écrit :
Guillaume Lelarge wrote:
> Magnus Hagander a écrit :
>> Guillaume Lelarge wrote:
>>> Magnus Hagander a écrit :
[...]
A super-quick primer to get going. First of all, cmake "prefers"
building outside the source directory, so here's a typical way to do it
(assuming your pgadmin di
Magnus Hagander a écrit :
> Guillaume Lelarge wrote:
>> Magnus Hagander a écrit :
>>> [...]
>>> A super-quick primer to get going. First of all, cmake "prefers"
>>> building outside the source directory, so here's a typical way to do it
>>> (assuming your pgadmin directory is "pgadmin3"):
>>>
>>> m
Guillaume Lelarge wrote:
> Magnus Hagander a écrit :
>> [...]
>> A super-quick primer to get going. First of all, cmake "prefers"
>> building outside the source directory, so here's a typical way to do it
>> (assuming your pgadmin directory is "pgadmin3"):
>>
>> mkdir ../pgadmin3-build
>> cd ../pga
Magnus Hagander a écrit :
> [...]
> A super-quick primer to get going. First of all, cmake "prefers"
> building outside the source directory, so here's a typical way to do it
> (assuming your pgadmin directory is "pgadmin3"):
>
> mkdir ../pgadmin3-build
> cd ../pgadmin3-build
> cmake -D CMAKE_INST
Guys,
I've just committed initial support for building pgadmin using cmake
instead of autoconf/autotools. Amongst other things, this leaves us with
*one* build system, on both Unix and Windows.
For now, the old system stays in there completely untouched, until we
can prove that this works on all