Hi,
On Tue, May 15, 2012 at 10:39 PM, Totte Karlsson
wrote:
> Hi,
> I have a project that depends on 3rd party dll's (libxml2).
>
> Is there a 'best practice' to deal with associated files, .h, .lib .dll of
> such within a CMake project?
>
> My library needs to link to the 3rd party lib, and need
My guess is that it has something to do with module files.
Michael
On 05/16/2012 08:31 AM, Petr Kmoch wrote:
> Anyone? Surely there must be a reason for adding those directories.
>
> Petr
>
> On Thu, May 10, 2012 at 9:25 AM, Petr Kmoch wrote:
>> Hi all,
>>
>> we're using cmake to generate Inte
Anyone? Surely there must be a reason for adding those directories.
Petr
On Thu, May 10, 2012 at 9:25 AM, Petr Kmoch wrote:
> Hi all,
>
> we're using cmake to generate Intel Fortran .vfproj files and some of
> my developers were asking why include directories in the project
> always include X an
Look at things involving the IMPORTED property of add_library. You probably
want to check the headers in to your repo. Or use or create a
FindLibXml2.cmake.
Or if you are compiling libxml2 as part of your build process, look at the
ExternalProject module.
Sent from my iPhone
On May 15, 2012
> I have a project that depends on 3rd party dll's (libxml2).
>
> Is there a 'best practice' to deal with associated files, .h, .lib .dll of
> such within a CMake project?
>
> My library needs to link to the 3rd party lib, and needs its dll for
> execution (obviously), so I feel the need for copyin
Hi,
I have a project that depends on 3rd party dll's (libxml2).
Is there a 'best practice' to deal with associated files, .h, .lib .dll of such
within a CMake project?
My library needs to link to the 3rd party lib, and needs its dll for execution
(obviously), so I feel the need for copying th
Hi all,
I experienced problems recently trying to use the CPack DEB packager
with components and wanted to share my solution (thanks partly to Eric
Noulard). The problem was with dependency generation in the Debian
control file using the CPACK_DEBIAN_PACKAGE_SHLIBS flag. Dependencies
would be gene
On Tue, May 15, 2012 at 2:14 PM, Eric Noulard wrote:
> 2012/5/15 Robert Dailey :
> >
> > On Tue, May 15, 2012 at 7:34 AM, Dave Abrahams
> wrote:
> >>
> >> For me, no. I'm trying to make a transition to CMake in a community
> >> where this is being seen as a problematic limitation.
> >
> >
> > I
2012/5/15 Robert Dailey :
>
> On Tue, May 15, 2012 at 7:34 AM, Dave Abrahams wrote:
>>
>> For me, no. I'm trying to make a transition to CMake in a community
>> where this is being seen as a problematic limitation.
>
>
> I actually was reading over the boost modularization discussion, but I
> did
Hi,
On Tue, May 15, 2012 at 12:00:09PM -0400, cmake-requ...@cmake.org wrote:
> Date: Tue, 15 May 2012 10:53:45 -0500
> From: Robert Dailey
> Subject: Re: [CMake] Secret precompiled header support?
> To: Dave Abrahams
> > > Is the current implementation really satisfactory?
> >
> > For me, no.
On Tue, May 15, 2012 at 7:34 AM, Dave Abrahams wrote:
>
> on Mon May 14 2012, Robert Dailey <
> rcdailey.lists-Re5JQEeQqe8AvxtiuMwx3w-AT-public.gmane.org> wrote:
>
> > Is improvement desired in this area?
>
> By me, yes.
>
By this, do you mean, you've taken an initiative to fix this yourself? If
Hi again,
I'm working on setting up install(...) commands for a shared library project
(call it libA), and I'm using the install(EXPORT ...) signature as has been
recommended to me previously to export the shared library target so I can
import it in another CMake-based project (call it libB). S
There was a long discussion about the limitations of ninja on each platform on
the mailing list just before the last release. That is where the decisions were
made to limit ninja to Linux only at this point.
That last thread was on April 17, 2012 with the title "Re: [CMake] CMake Ninja
generato
Can someone explain why a ninja generator isn't available everywhere
that ninja runs? Can this be remedied?
Thanks,
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opens
on Mon May 14 2012, Robert Dailey
wrote:
> Is improvement desired in this area?
By me, yes.
> Is the current implementation really satisfactory?
For me, no. I'm trying to make a transition to CMake in a community
where this is being seen as a problematic limitation.
--
Dave Abrahams
Boo
I have done this, but adding it "int other way" . Selecting on the screen
the line where the error araises and exploring until finding qmake.exe (in
the same folder you indicate). And I think it works.
Thank you
2012/5/15 Sweety Pie
> Hey there,
> Please try this, it may work
>
> 1- Open CMake -
Hi Gonzalo,
the problem is cmake didn't find qmake. The safest way to use cmake
with Qt on Windows is to run cmake from a Qt-aware command line (or
have qmake in your PATH). There should be a shortcut to a "Qt command
prompt" installed in your Start menu. If it's not, you can create your
own:
`%C
Hey there,
Please try this, it may work
1- Open CMake - cmake-gui (on the Desktop) - if you are using win7 make
sure you open the program in administrator mode - right click on the icon
and click on "run as administrator".
2- Click on "Add Entry" again
Set name to QT_QMAKE_EXECUTABLE
18 matches
Mail list logo
