Hello,
A small correction to my previous post (see below). It should have
read *local* target wherever I said *custom* target. Anyhow, the
actual problem should remain the same:
I would need to have local targets override imported targets of the
same name. And the only solution I a came
On 24-11-2010 at 17:34, in message
ddc068a445e2cc6dcf015e9b84217da0.squir...@webmail.sf-mail.de, Rolf
Eike
Beer e...@sf-mail.de wrote:
On Wed, Nov 24, 2010 at 6:57 AM, Rolf Eike Beer e...@sf-mail.de
wrote:
In KDE we have a macro MACRO_WRITE_BASIC_CMAKE_VERSION_FILE()
which
helps
with
On 24-11-2010 at 17:45, in message
20101124164507.gg23...@cryptio.net, Tyler
Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 12:11:56PM +0100, Micha Renner wrote:
SET(CMAKE_INSTALL_PREFIX /foo/bar CACHE PATH Foo install
prefix)
So, without the test to
2010/11/25 Marcel Loose lo...@astron.nl:
Everyone looks into his local CMake documentation and uses what he
finds
in there. And then it breaks on older versions. You currently have
no
chance to know what works but to install all older versions and do a
binary search in the documentation.
If I install using this kind of stuff
INSTALL (
FILES ${PROJECT_BINARY_DIR}/H5pubconf.h
DESTINATION ${HDF5_INSTALL_INCLUDE_DIR}
COMPONENT headers
)
and
INSTALL (
EXPORT ${HDF5_EXPORTED_TARGETS}
DESTINATION
I currently use mingw and I noticed that in the linking phase the
following options appear without specifying nothing of that:
-lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32
-luuid -lcomdlg32 -ladvapi32
How can avoid this?
___
On Wednesday 24 November 2010 19:03:21 David Cole wrote:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer e...@sf-mail.de wrote:
So I think it is _really_
On Thursday 25 November 2010, Johannes Zarl wrote:
On Wednesday 24 November 2010 19:03:21 David Cole wrote:
On Wed, Nov 24, 2010 at 12:58 PM, Tyler Roscoe ty...@cryptio.net wrote:
On Wed, Nov 24, 2010 at 11:41:46AM -0500, David Cole wrote:
On Wed, Nov 24, 2010 at 11:34 AM, Rolf Eike Beer
On 11/24/2010 04:51 PM, Johannes Zarl wrote:
Hi,
On 11/23/2010 at 21:25, Alexander Neundorf a.neundorf-w...@gmx.net wrote:
CMAKE_MODULE_PATH is only for finding Find-modules, not for finding the
actual packages or Config-files.
For that you can set CMAKE_PREFIX_PATH. CMake uses each
On 11/23/2010 03:23 PM, Andrea Galeazzi wrote:
Marcel Loose ha scritto:
On 23-11-2010 at 10:55, in message 4ceb8f76.80...@korg.it, Andrea
Galeazzi
galea...@korg.it wrote:
In a project I've got two groups of files having different include
paths. These paths have some conflicts
10 matches
Mail list logo