It didn't help very much though :S
Now I get:
COMMAND if [ ! -e TEST ]; then echo ok && echo 2 && echo "test"; fi
==>
if [ ! -e TEST "];" then echo ok "&&" "echo \"test\";" ">/dev/null" fi
So clearly the first case was better :)
On 28/01/2008, Steven Van Ingelgem <[EMAIL PROTECTED]> wrote:
> No
No :)
Thanks for pointing this out!
On 28/01/2008, Brandon Van Every <[EMAIL PROTECTED]> wrote:
> On Jan 27, 2008 9:20 PM, Steven Van Ingelgem <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> >
> > I'm working on a SLES10.
> >
> >
> > I have an "add_custom_command" with in it's command:
> >
> > LDFLAGS=
On 2008-01-27 22:28-0500 Brandon Van Every wrote:
On Jan 27, 2008 8:34 PM, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
I would like to be able to read arbitrary environment variables from within
cmake. The 2.4.8 documentation only refers to $ENV once as "$ENV{PATH}" in
an extremely narrow context
On Jan 27, 2008 9:20 PM, Steven Van Ingelgem <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> I'm working on a SLES10.
>
>
> I have an "add_custom_command" with in it's command:
>
> LDFLAGS="-L${PROJECT_SOURCE_DIR}/lib -ldl" ./configure ...etc...
>
> Now if I go and check the configure log, I see that the LD
On Jan 27, 2008 8:34 PM, Alan W. Irwin <[EMAIL PROTECTED]> wrote:
> I would like to be able to read arbitrary environment variables from within
> cmake. The 2.4.8 documentation only refers to $ENV once as "$ENV{PATH}" in
> an extremely narrow context (the TO_CMAKE_PATH signature of the FILE comman
Hi,
I'm working on a SLES10.
I have an "add_custom_command" with in it's command:
LDFLAGS="-L${PROJECT_SOURCE_DIR}/lib -ldl" ./configure ...etc...
Now if I go and check the configure log, I see that the LDFLAGS are
interpreted as "-L${PROJECT_SOURCE_DIR}/lib\ -ldl" (watch the escaping
of the
Andreas Pakulat wrote:
Also I noticed that the linker line doesn't contain an option that gives
gcc the kde4 library dir to search for kde libs. This is another thing
which broke things for me here, i.e. ld complains that -lsolid cannot be
found (as you can see below there's a solid entry in the
I would like to be able to read arbitrary environment variables from within
cmake. The 2.4.8 documentation only refers to $ENV once as "$ENV{PATH}" in
an extremely narrow context (the TO_CMAKE_PATH signature of the FILE command).
However, when I tried, e.g.,
SET(pc_path "$ENV{PKG_CONFIG_PATH}")
Andreas Pakulat wrote:
Anyway, the latest cvs version from cmake (update 2 hours ago) produces
the following entries in KDELibsDependencies.cmake. This file is
generated using the export_library_dependecies() command:
SET(kdecore_LIB_DEPENDS
"general;/home/andreas/qt-copy/lib/libQtCore.so;gener
Hello again,
Sorry what I stated before does not work either. I thought it did, but it does
not. EXCLUDE_FROM_ALL does not seem to work for me. Perhaps I am
mis-understanding its intent or I am doing something else. Hope someone can
provide some insight about this issue. Thanks.
Here is what
Hi,
I figured this out on my own. Apparently if the CMakeLists.txt file in the
mentioned sub-directoy contains a INSTALL rule, the EXCLUDE_FROM_ALL
parameter does not apply. If I add the "OPTIONAL" directive to the INSTALL
target, then all works as advertised.
The question I now have is that s
Hi,
Using a CVS version from a few minutes ago, I receive this:
cmake: /src/CMake/Source/cmLocalGenerator.cxx:2224: std::string
cmLocalGenerator::ConvertToRelativePath(const
std::vector,
std::allocator >, std::allocator, std::allocator > > >&, const char*):
Assertion `in_remote[0] != '\"'' faile
Hello,
I recently updated my cmake installation from cvs and now I can't get
it to configure for 'Unix Makefiles'. I am now getting this error:
...
Performing Test curl_cv_recv
Performing Test curl_cv_recv - Failed
CMake Error: Unable to link function recv
...
I'm using the same cvs download, bu
Hello,
The documentation for ADD_SUBDIRECTORY suggests states the following:
If the EXCLUDE_FROM_ALL argument is provided then this subdirectory will not
be included in build by default. Users will have to explicitly start a build
in the generated output directory. This is useful for having cma
On 27.01.08 14:50:13, Aleix wrote:
> I am compiling KDE with the cmake-cvs version.
>
> I had the same problem when I switched and, IIRC, I had to (nuke every
> builddir and) recompile whole KDE because of this -lgeneral thing, but
> this was back in the summer so I think it is not a new issue.
I
Hi andreas,
I am compiling KDE with the cmake-cvs version.
I had the same problem when I switched and, IIRC, I had to (nuke every
builddir and) recompile whole KDE because of this -lgeneral thing, but
this was back in the summer so I think it is not a new issue.
Bye!
Aleix
On 1/26/08, Andreas Pa
16 matches
Mail list logo
