Hi,
can sombody tell me why ${OUTPUT} is empty?
I don't see any reason why it should not work with msvc. Can sombody
give me a hint where to look for in the sourcecode?
Christian
signature.asc
Description: OpenPGP digital signature
___
CMake mailing
I'd have to vote for this as a "feature" actually. I think
"$ENV{something}" should evaluate to exactly the value of the
environment variable and nothing more. Any transformations have to be up
to the user because we can't know what the environment variable
represents...
Having said that... p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Ehrlicher wrote:
> Hi,
>
> can sombody tell me why ${OUTPUT} is empty?
> I don't see any reason why it should not work with msvc. Can sombody
> give me a hint where to look for in the sourcecode?
>
> Christian
AFAIK there is no predefined
Sylvain PRAT wrote:
In fact, I meant duplicate copies for *release* versions :
relwithdebufinfo, minsizerel and release. That is, is there a
CMAKE_MINSIZE_POSTFIX, CMAKE_RELWITHDEBUG_POSTFIX or something like that?
This was added a few weeks in the development version. It will be
included in
Christian Ehrlicher wrote:
can sombody tell me why ${OUTPUT} is empty?
I don't see any reason why it should not work with msvc. Can sombody
give me a hint where to look for in the sourcecode?
This is a problem with VCExpress 2005 only because the tool itself does
not produce output. CMake is
David Cole wrote:
> I'd have to vote for this as a "feature" actually. I think
> "$ENV{something}" should evaluate to exactly the value of the
> environment variable and nothing more. Any transformations have to be up
> to the user because we can't know what the environment variable
> represent
I have a "global" variable in my top level CMakeLists.txt file. I want
code in CMakeLists files in subdirectories to add values to it.
Unfortunately the modifications that are made are lost after I leave the
subdirectory.
Is there any way to get information passed up the tree of CMakeLists fi
Hi,
the attached patch does two things:
1) Bugfix: it detects the correct path for the created executable via
GetProperty("LOCATION") instead of simply doing
${CMAKE_CURRENT_BINARY_DIR}+TARGET_NAME.
2) Additionally to the kdevelop project file *.kdevelop and the file list
file *.kdevelop.fi
I've compiled CMake 2.3-20060213 from CVS sources using MinGW and MSYS.
./bootstrap and make work fine. No build errors, and I seem to have
everything. When I do "make install," nothing is installed. At first I
thought it was that intermediate paths like /usr/local didn&
Brandon J. Van Every wrote:
I've compiled CMake 2.3-20060213 from CVS sources using MinGW and
MSYS. ./bootstrap and make work fine. No build errors, and I seem to
have everything. When I do "make install," nothing is installed. At
first I thought it was that intermediate
10 matches
Mail list logo