2011/7/18 Daniel Franke :
>>
>> Could you explain why you need CPack to be included here?
>>
>> If the requirement comes from the needed definition of
>> "cpack_add_component" then you can try to do the following:
>
> Exactly for this reason.
>
>
>> 1) include(CPackComponent) early enough
>> in
When cross compiling, only some the qmake queries are actually used.
Finding the rest just works if subdirs in the Qt installation weren't given
different values when running Qt's configure script (e.g. --libdir=mylib or
--libdir=lib/qt4).
So, the root of the Qt installation needs to be given
Hi Kevyn-Alexandre,
May be you could so something like:
file(READ "/path/to/Config-Generic.txt" configGenericContent)
file(READ "/path/to/Config-Project.txt" configProjectContent)
file(WRITE "/path/to/CMakeCache.txt ${configGenericContent})
file(APPEND "/path/to/CMakeCache.txt ${configProjectCont
Hi,
Is it possible to call or include CMakeCache from another CMakeCache?
I want to replace my 2 CMakeCache to one.
ex:
cmake -C Config-Generic.txt Config-Project.txt ../
Any idea if it's possible to include the Config-Generic.txt inside the
Config-Project.txt?
Best Regards,
Kevyn-Alexandr
On Mon, Jul 18, 2011 at 07:23:26AM -0700, clin...@elemtech.com wrote:
> What version of cmake are you using?
$ cmake --version
cmake version 2.8.4
> And since you are cross-compiling, what does your toolchain file for
> cmake look like?
The contents of my toolchain.cmake file:
set(CMAKE_
Hi Eric.
On Monday 18 July 2011 09:36:37 Eric Noulard wrote:
> http://public.kitware.com/Bug/view.php?id=11808
Thanks for the link.
> > Maybe I should have provided an example. At 3am, things start to get
> > fuzzy around the edges ...
> >
> > I defined a bunch of macros, e.g.
> >
> >myp
Hi all,
I'm facing the following problem trying to generate the dependencies
tree of an executable. I have a working area
/path/to/my/working/area/MyPackage
with, say, one executable I want to build. The relevant CMakeLists.txt
line is something like:
add_executable(App src/App.cc)
target_
Thanks for the link -- it at least tells me about the error message that I'm
receiving. The problem is that I haven't set 'CONF=Release' as part of any
directory path. CONF=Release seems to be a configuration flag. I'm thinking
that it's supposed to be getting added to the command line like
JC,
thx I may have send the email a bit to fast
Kevyn-Alexandre
On 2011-07-15, at 11:39 PM, Jean-Christophe Fillion-Robin wrote:
> Hi Kevyn-Alexandre,
>
> Indeed, you can get or set environment variable from CMake.
>
> For example:
> set(ENV{PATH} "/path/to/foo:$ENV{PATH}")
>
> Hth
> Jc
What version of cmake are you using? And since you are cross-compiling, what
does your toolchain file for cmake look like? Did you add a find path in that
file for your powerpc libs?
The spec file only applies on qmake generated makefiles, which is not happening
when using cmake.
And you do not
Hi Hugh,
By design ExternalProject module will download and patch a project only one
time.
Indeed, the ExternalProject wouldn't be able to apply a patch more than one
time. It also doesn't have a way to detect if a patch has been applied.
In other word, you will have to clear the project so tha
Hi everybody,
We have a very big project using rules written with Imake and we want to switch
to Cmake.
Everything is more or less ok, except few things related to code generated.
We have some .idl files (Corba syntax) used to generate custom C++ wrappers in
order to be able to have POD for shar
Hi,
On Sun, Jul 17, 2011 at 11:16:56PM +0200, Daniel Franke wrote:
> > IMHO install stuff is ideally (i.e., usually) supposed to be done
> > _exactly after_ all targets within the build space have become available.
>
> How so? Let there be tool01 to toolNN. Let each tool reside in its own
> dir
2011/7/17 Daniel Franke :
>
> Hi Andreas.
>
> On Sunday 17 July 2011 21:36:26 Andreas Mohr wrote:
>> to me it sounds like all the effects can simply be described as
>> happening due to including CPack way too early.
>> Verdict: Don't Do That (tm)
>
> Maybe. See below for more details.
There exists
Hi!
I'm trying to cross-compile a Qt-application for the powerpc platform.
CMake looks for the Qt libraries in the wrong place - it finds the host
libraries instead of the target libraries:
Warning: QT_QMAKE_EXECUTABLE reported QT_INSTALL_LIBS as /usr/lib
Warning: But QtCore couldn't be f
15 matches
Mail list logo