Hi folks,
I'm using VS2012+cmake2.8.12. My problem is that CMake failed to generate
the correct path to my external project. For example:
Project("{...}") = "external", "external.vcxproj", "..."
whereas 'external.vcxproj' should be something like
..\path\to\external.vcxproj
Here is how I use Ex
All,
I'm building FLTK as an ExternalProject to a 'Libraries' project. Inside
the ExternalProject, I'm using the FLTK CMake build system.
I've then created a SuperProject to build Libraries as an ExternalProject
(and my main project too). This works great so far on my Mac.
On my Windows machin
On Thursday, February 06, 2014 08:45:52 AM a.gri...@erhardt-leimer.com wrote:
> Hey Mister Neundorf,
>
> thanks for the quick reply. Problems apear not with the generated files
> explicit, but with the linked resources in general. In our case the "GDB
> Hardware Debugging" and the "Subversive" Plu
Alan W. Irwin wrote:
> I assume you could do
> that by including a common file in each of your subprojects, but I
> have never had to do that (my project only has two calls to
> cmake_minimum_required which are easy to keep in synch manually) so I
> will let others comment on details of the implem
On 2014-02-06 11:09-0800 Rob McDonald wrote:
Is there a way to get cmake to report back an _actual_ minimum required
version?
Our project has lots of parts, and the CMakeLists.txt have not been very
well maintained. Right now, CMAKE_MINIMUM_REQUIRED is set to different
values throughout, none
Is there a way to get cmake to report back an _actual_ minimum required
version?
Our project has lots of parts, and the CMakeLists.txt have not been very
well maintained. Right now, CMAKE_MINIMUM_REQUIRED is set to different
values throughout, none of which are likely correct.
It seems like it '
Don't forget to register for Kitware's CMake course in Santa Fe. Early
registration ends February 12, 2014.
http://training.kitware.fr/browse/52
-Bill
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers
On Thu, Feb 6, 2014 at 1:14 AM, PCMan wrote:
> libqtxdg - a base lib required by others
> liblxqt - a library depends on libqtxdg
> lxqt-config - a tool depends on liblxqt and libqtxdg.
> To build lxqt-config, liblxqt and libqtxdg need to be "installed" first.
The key is whether you can avoid t
That was it! Great stuff! Thank you for the help Johannes and Rolf!
On Thu, Feb 6, 2014 at 12:46 PM, Johannes Zarl wrote:
> On Thursday, 6. February 2014, 13:30:54, Ramin Kamal wrote:
> > Thanks! I tried that, but it still finds the system library. Here's my
> test
> > setup:
>
> I tried with b
On Thursday, 6. February 2014, 13:30:54, Ramin Kamal wrote:
> Thanks! I tried that, but it still finds the system library. Here's my test
> setup:
I tried with basically the same steps, and it works for me.
>
> % cd /usr/lib
> % cp libjpeg.* /tmp/myjpeg/lib/
> [...]
> -- Found JPEG: /usr/lib64/l
Thanks! I tried that, but it still finds the system library. Here's my test
setup:
% cd /tmp
% mkdir myjpeg myproj
% cd myjpeg
% mkdir lib include
% cd /usr/lib
% cp libjpeg.* /tmp/myjpeg/lib/
% cd /usr/include
% cp jpeglib.h /tmp/myjpeg/include/
% cd /tmp/myproj
% cat << EOF > CMakeLists.txt
cma
Am 06.02.2014 13:02, schrieb Ramin Kamal:
Hi,
I'm trying to build an open source package (openimageio, if it matters)
and
would like to have cmake use a specific build of the jpeg library for
that
project. It looks like the jpeg library that's used is determined in
the
line:
find_package (J
Hi,
I'm trying to build an open source package (openimageio, if it matters) and
would like to have cmake use a specific build of the jpeg library for that
project. It looks like the jpeg library that's used is determined in the
line:
find_package (JPEG REQUIRED)
So I'd like to modify the behavio
On 06/02/14 07:14, PCMan wrote:
> Hello,
> I'm PCMan, one of the developers of LXDE desktop (now LxQt after
> merged with Razor-qt project).
> http://lxde.org/ and http://razor-qt.org/
>
> We're migrating from gtk+ to Qt and autotools to CMake and encountered
> some issues.
> There are many small m
14 matches
Mail list logo